Skip to main content
Glama

Conversões atribuídas

pixel_get_conversions
Read-only

Lista SÓ as conversões com clique CASADO (atribuição completa: clique → venda), com campanha/adset/ad herdados do clique e o status de envio ao CAPI. Para a lista completa de vendas (inclusive sem clique), use pixel_get_shopee_sales. Paginação: total/count/offset/has_more.

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

Input Schema

NameRequiredDescriptionDefault
daysNoJanela em dias se start/end ausentes (1–366, default 30).
limitNoMáximo de conversões (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

A4.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 adds useful, non-annotation context: attribution semantics, the inherited click fields, the CAPI send status, and the pagination payload keys (total/count/offset/has_more) — valuable since no output schema exists. It still says nothing about defaults, maximum window behavior, or empty-result handling.

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 tight sentences, front-loaded with the scope constraint (SÓ conversões com clique CASADO), then the alternative route, then pagination. No filler; the terse "total/count/offset/has_more" shorthand still carries real 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?

For a read-only reporting tool with zero required parameters, full schema coverage, and no output schema, the definition covers scope, routing, and return/pagination shape well. It stops short of describing the fields of a conversion record itself (value/currency/timestamps), which an agent must discover by calling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all five parameters (days, start_date, end_date, limit, offset) are already documented with ranges and defaults, setting a baseline of 3. The description contributes the offset-based pagination model and response keys, giving marginal meaning beyond the schema but no extra guidance on the days-vs-start/end precedence.

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 a sharply scoped resource (only conversions with a CASADO/matched click, full click→sale attribution) and names the fields it returns (campaign/adset/ad inherited from the click, CAPI status). The contrast with pixel_get_shopee_sales makes the scope unambiguous 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?

Explicitly routes the agent: use pixel_get_shopee_sales for the full sales list including those without a click, use this one only for click-matched conversions. That is a named alternative plus the condition that selects it, leaving nothing to inference.

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