Skip to main content
Glama

Resumo do painel

pixel_get_dashboard_summary
Read-only

Visão geral da conta no período: investimento (spend Meta), cliques rastreados, vendas Shopee, comissão, ROAS, EPC e taxa de conversão. Valores monetários em centavos de BRL.

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_dashboard_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoJanela em dias se start/end ausentes (1–366, default 30).
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. Changed5 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 / start_date / pattern
      Added value: +"^\\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12]\\d|3[01])$"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description does add real value beyond that by naming the source semantics of each metric (spend from Meta, clicks tracked, sales from Shopee) and declaring that monetary values are in centavos de BRL, which prevents a costly unit error. It stops short of describing aggregation behavior (timezone handling, what happens with no data).

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 sentences, front-loaded with the scope and then the metric list; the unit caveat is placed last where it belongs. The metric enumeration is dense but each item is informative, so little is wasted.

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

Completeness3/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 must convey the return payload; it does so by listing the metrics and the currency unit, which is adequate. However, it omits the shape of the response (single object vs. nested fields) and behavior when the period has no data, leaving gaps for a metrics tool whose result is the whole point.

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 days, start_date and end_date are already documented with formats, defaults and the days-fallback rule. The description only says "no período" and adds no detail on date precedence or UTC handling beyond the schema, which matches the baseline 3 when the schema carries the load.

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-like purpose ("Visão geral da conta no período") and enumerates the metrics returned: investimento (spend Meta), cliques rastreados, vendas Shopee, comissão, ROAS, EPC e taxa de conversão. This distinguishes it as a consolidated overview versus the narrower sibling metrics tools, though it never names those siblings explicitly.

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?

"Visão geral da conta no período" implies the aggregate-overview use case, but there is no explicit when-to-use guidance, no mention of when a caller should prefer pixel_get_roas or pixel_get_shopee_sales instead, and no prerequisite notes. Usage is inferable rather than stated.

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