Skip to main content
Glama

Amazon Seller MCP Server — AgentXray

Profit by SKU

get_profit_by_sku
Read-onlyIdempotent

Per-SKU profit ranking for the connected seller account over a window: units, revenue, fees, COGS, net profit and margin per SKU. Use this for 'which product makes money', 'which SKU is losing money', 'what should I stop selling'.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_profit_by_sku"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoONE calendar day instead of a window: 'yesterday', 'today' or YYYY-MM-DD (within the last 365 days). The day is the STORE's own day in its marketplace's timezone. Use it for 'how was yesterday' or a named date; do not also pass days.
daysNoWindow in days, 1-365 (default 7, as the app).
limitNoMax SKUs (default 20, max 50).
end_dateNoLast day of the custom range, YYYY-MM-DD (inclusive).
start_dateNoFirst day of a custom range, YYYY-MM-DD on the STORE's calendar (inclusive). Pass with end_date for 'September', 'between X and Y' or any past period; it replaces days. At most 730 days.
marketplace_idNoOptional marketplace filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is disclosing the returned metric set and the account/window scoping. It does not mention the default/max SKU cap or any ranking behavior, but with annotations carrying the operational burden the remaining gap is minor.

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?

Two sentences: the first front-loads what is returned, the second front-loads when to use it. No filler, no restatement of the title, and it ends before becoming a tutorial.

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?

With no output schema, the description compensates by enumerating the fields returned (units, revenue, fees, COGS, net profit, margin), which is exactly the information an agent needs to decide whether this tool answers its question. Combined with 100% parameter coverage, an agent can call this correctly without further inference.

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% — every parameter has a documented meaning including the date-vs-days-vs-range precedence rules — so the schema does the heavy lifting. The description adds only the vague phrase 'over a window' and no syntax or precedence detail beyond the schema. Baseline 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?

Specific verb+resource ('Per-SKU profit ranking') with the exact metric set enumerated (units, revenue, fees, COGS, net profit, margin) and a scope ('connected seller account over a window'). The 'per-SKU' framing cleanly separates it from the sibling get_profit_summary.

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?

Gives three concrete trigger questions ('which product makes money', 'which SKU is losing money', 'what should I stop selling') that map well onto an agent's intent space. It stops short of naming alternatives — e.g. when to prefer get_sku_trend or get_profit_summary instead — so it is clear context without exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources