Skip to main content
Glama

Vendas Shopee

pixel_get_shopee_sales
Read-only

Lista TODAS as vendas Shopee rastreadas do período (grão = item da conversão), inclusive as sem clique casado. Mostra status, GMV e comissão (centavos) e a atribuição (campaign/adset/ad) quando disponível. Paginação: total/count/offset/has_more/next_offset.

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

Input Schema

NameRequiredDescriptionDefault
daysNoJanela em dias se start/end ausentes (1–366, default 30).
limitNoMáximo de vendas (1–200, default 50).
offsetNoDeslocamento para paginação (default 0).
end_dateNoFim (yyyy-mm-dd, UTC). Opcional (default hoje).
start_dateNoInício (yyyy-mm-dd, UTC). Opcional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • addedInput schema / properties / days / maximum
      Added value: +366
    • addedInput schema / properties / days / minimum
      Added value: +1
    • changedInput schema / properties / days / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / end_date / pattern
      Added value: +"^\\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12]\\d|3[01])$"
    • addedInput schema / properties / limit / maximum
      Added value: +200
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / offset / minimum
      Added value: +0
    • changedInput schema / properties / offset / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / start_date / pattern
      Added value: +"^\\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12]\\d|3[01])$"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description's added value is in disclosure of the data grain (one row per conversion item), the inclusion of unattributed sales, the fact that commission is expressed in cents, and the attribution fields available only 'quando disponível'. Missing only operational traits such as rate limits or freshness/latency of tracked sales.

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 scope statement is front-loaded in the first clause, followed by what is returned and how pagination behaves, with no filler sentences. Each clause (all sales, grain, unmatched-click inclusion, units in cents, pagination keys) carries distinct information.

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

Completeness4/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 usefully names the returned fields (status, GMV, commission in cents, attribution) and the pagination envelope keys, which compensates for the missing output contract. For a read-only listing tool with fully documented parameters, only minor gaps remain, such as what an absent attribution looks like in output.

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% and every parameter (days, limit, offset, start_date, end_date) is already described with ranges and defaults, so the baseline is 3. The description only reiterates the period concept and lists pagination response keys, which are return-value facts rather than added parameter meaning.

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

Purpose4/5

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

States a specific verb and resource ('Lista TODAS as vendas Shopee rastreadas do período') and sharpens scope with the grain definition ('grão = item da conversão') plus the inclusion of sales with no matched click. It does not name a sibling to contrast with (e.g. pixel_get_commissions or pixel_get_conversions), so differentiation is only partial.

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

Usage Guidelines3/5

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

Usage is implied by the period-based framing and the default windows documented in the schema, but there is no explicit when-to-use/when-not guidance and no pointer to the sibling tools that return aggregate commissions or conversions. The agent must infer that this is the raw per-sale listing versus the aggregate endpoints.

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