MerchantFlow

Markets Overview

get_markets

Read-onlyIdempotent

Get the Markets dashboard table for a date range, including real geo ad spend, blended fallback spend, revenue, net profit, margins, ROAS, POAS, CAC, and spend-without-orders markets.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of markets to return after sorting (default 50, hard-capped at 100).
`sort_by`	No	Metric to sort markets by, highest first. 'dashboard' (default) uses the dashboard's own net-profit-based ordering; other values sort directly by that metric: net_profit, revenue, orders, spend, net_margin_pct, roas, poas, cac.
`end_date`	Yes	End of the date range in YYYY-MM-DD format, resolved in the tenant's timezone (inclusive).
`start_date`	Yes	Start of the date range in YYYY-MM-DD format, resolved in the tenant's timezone (inclusive); clamped forward to the plan's history window if it reaches further back than allowed.
`country_codes`	No	Restrict results to these ISO 3166-1 alpha-2 shipping country codes (up to 50); omit to return every market with activity in the period.
`include_spend_without_orders`	No	Include markets that had ad spend but no orders in the period (default true); set to false to hide spend-without-orders markets.

Output Schema

TableJSON Schema

Name	Required	Description
`_meta`	No
`period`	No
`filters`	No
`markets`	No
`summary`	No
`_message`	No
`coverage`	No
`currency`	No
`metadata`	No
`_truncated`	No
`_tenant_context`	No
`history_clamped`	No	Null when the requested range fell inside the plan history window.
`total_matching_markets`	No	Markets matching the filters before `limit` was applied.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 20, 2026

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is established. The description adds useful behavioral context by specifying that results include real geo ad spend, blended fallback spend, revenue, net profit, margins, ROAS, POAS, CAC, and spend-without-orders markets.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence that opens with the action and resource and then enumerates the included metrics. It is concise, information-dense, and contains no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the rich parameter schema, output schema, and annotations, the description covers the essential intent and output scope. Nothing critical for selecting or invoking the tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with detailed parameter descriptions for start_date, end_date, limit, sort_by, country_codes, and include_spend_without_orders. The tool description does not add parameter-level meaning beyond the schema, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: 'Get the Markets dashboard table for a date range'. It lists the exact metrics included, making the tool's purpose unmistakable and distinguishing it from related market/product tools like get_market_products.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly states the tool returns the Markets dashboard table for a date range, so an agent knows when this tool is appropriate. It does not explicitly name alternatives or exclusions, but the context is clear enough for selection among the many sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All MerchantFlow tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?