Skip to main content
Glama

rr_list_sales_history

Read-onlyIdempotent

Retrieve paginated sales history by SKU, store, or time range to analyze daily or monthly demand. Use cursor values to page through results and determine window totals for planning.

Instructions

Get sales history rows, newest first, over a time period. total is the exact number of rows in the window; count is the rows in this page. When has_more is true, pass next_cursor as cursor to get the next page. Totals and rankings come from total or rr_list_top_sellers; a partial walk of the rows says nothing about the whole window.

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": "rr_list_sales_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
skuNoFilter by SKU
daysNoLookback days (default 30, max 90)
limitNoRows per page (default 1000, max 5000).
cursorNonext_cursor from the previous page. Pass it with the same other inputs until has_more is false.
monthsNoMonths of history when granularity is month (default 12, max 36). Net demand units; the newest month may be partial.
store_idNoOnly sales from this store.
granularityNoday (default) returns daily rows for up to 90 days. month returns one row per calendar month for up to 36 months, for one SKU or, with no SKU, the store's totals.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare this a safe, idempotent, closed read, but the description goes further by naming the response fields (total, count, has_more, next_cursor) and explaining the distinction between total window size and current page size. With no output schema present, this disclosure of return shape and the warning about interpreting partial pages is exactly the extra context an agent needs.

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?

Three sentences, front-loaded with the primary action, then pagination mechanics, then the interpretation caveat. Every sentence carries distinct information with no filler or repetition of the tool name.

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?

For a paginated read tool with no output schema, the description covers result ordering, pagination contract, the meaning of both count fields, and the correct alternative for aggregate/ranking questions. An agent has everything required to call it correctly and interpret the response.

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 coverage is 100%, so all seven parameters including granularity, days, months, and cursor are already documented in the input schema. The description only links the returned next_cursor back to the cursor parameter, adding minimal meaning beyond the schema; the baseline 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 opens with a specific verb and resource ("Get sales history rows"), states ordering ("newest first") and scope ("over a time period"). It explicitly distinguishes itself from rr_list_top_sellers, so an agent can pick between them without opening either schema.

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

Usage Guidelines5/5

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

It gives an explicit when-to-use-me-else rule: totals and rankings should come from total or rr_list_top_sellers, and a partial walk of rows "says nothing about the whole window." It also documents the pagination loop condition (has_more true → pass next_cursor as cursor), which is operationally necessary guidance.

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