Pixaro

Return Order Analytics Dashboard data for one store and an inclusive store-local date range. Use this for totals, channel and status breakdowns, item-match outcomes, order trends, peak hours, and top-selling items; do not use it to look up one order.

get_order_analytics

Return the breakdown and linked orders for one payout_reference_id returned by get_payouts.

get_payout_details

Return Payout Dashboard data for one store and an inclusive store-local date range, including payout summaries, cards, charts, fees, taxes, promotions, adjustments, order value, and markup.

get_payouts

Search individual orders for one store in an inclusive store-local date range. Use filters and pagination for order investigation; this tool is not an aggregate analytics report. The default deployment returns 100 records per page and accepts at most 100 per page; operators configure these values with MCP_SEARCH_DEFAULT_PAGE_SIZE and MCP_SEARCH_MAX_PAGE_SIZE. A search with more than the configured MCP_SEARCH_MAX_MATCHING_RECORDS limit (1,000 by default) is rejected, even for the first page. Use pagination.next_offset to request the next page.

search_orders

Search POS transactions. Use start_date and end_date for store-local calendar reporting, or start_datetime and end_datetime for exact RFC3339 instants. Returned timestamps include UTC, store-local time, and timezone when available. Use transaction_details_url to open the transaction details page in Pixaro, where CCTV recordings can be viewed when available. The default deployment returns 100 records per page and accepts at most 100 per page; operators configure these values with MCP_SEARCH_DEFAULT_PAGE_SIZE and MCP_SEARCH_MAX_PAGE_SIZE. A search with more than the configured MCP_SEARCH_MAX_MATCHING_RECORDS limit (1,000 by default) is rejected, even for the first page. Use pagination.next_cursor as cursor for the next page.

search_transactions