Skip to main content
Glama

Por sub_id

painel_get_subid_breakdown
Read-onlyIdempotent

Vendas agrupadas pelo VALOR BRUTO de um nível de sub_id (Shopee Sub_id1..5 e equivalentes): pedidos, itens, comissão e GMV por valor — os 50 de maior comissão. Use quando o afiliado marca campanha/grupo/post no sub_id e ainda não criou etiquetas. availableLevels diz quais níveis têm dado.

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

Input Schema

NameRequiredDescriptionDefault
daysNoAlternativa a start/end: janela de N dias terminando em end_date (default 30).
levelNoNível do sub_id (default 1).
end_dateNoFim do período (yyyy-mm-dd). Opcional (default: hoje).
start_dateNoInício do período (yyyy-mm-dd). Opcional — ex.: "2026-06-01".
marketplaceNoFiltra por marketplace (slug). Opcional. Valores: shopee, amazon, mercadolivre, aliexpress, awin, cityads, rakuten, magalu, natura, terabyte, paguemenos, belezanaweb, outros.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the bar is lower. The description adds two things annotations cannot: results are truncated to the top 50 by commission, and an `availableLevels` field in the response indicates which levels actually have data — important for interpreting empty results. No output schema exists, so more return detail would have helped.

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

Conciseness4/5

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

Two dense sentences, front-loaded with the aggregation and followed by the usage condition. The em-dash clause efficiently packs the returned metrics and the 50-row cap, though the sentence is long enough to be slightly heavy for a quick scan.

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 compensates by naming the returned metrics, the row cap, and the `availableLevels` signal. Combined with rich annotations and a fully documented schema, an agent has enough to invoke and interpret it correctly; only the shape of each row is left unspecified.

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%, so the schema already documents days, level, start/end dates and marketplace. The description only reinforces the sub_id level concept (Sub_id1..5 and equivalents) without adding format or default semantics beyond what the schema states.

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?

States a specific verb and resource: sales grouped by the gross value of a sub_id level, listing the metrics returned (orders, items, commission, GMV). It also implicitly distinguishes itself from the tag-based sibling by noting the sub_id route is for affiliates who have not created tags yet.

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?

"Use quando o afiliado marca campanha/grupo/post no sub_id e ainda não criou etiquetas" gives a concrete selection condition and hints at the tags alternative. It stops short of naming the sibling tool (e.g. painel_get_tag_performance) or stating an explicit when-not case.

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