Skip to main content
Glama

Comissão por campanha

pixel_get_commissions
Read-only

Comissão (centavos de BRL) no período quebrada por campanha Meta, com pedidos, itens, GMV, spend e ROAS (basis points). netCommission == totalCommission (afiliado direto).

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

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
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely non-obvious semantics the schema cannot express: monetary values are in centavos de BRL, ROAS is expressed in basis points, and netCommission equals totalCommission for a direct affiliate. It does not mention whether commissions are provisional or settled, but the unit and identity disclosures are substantive.

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?

A single sentence that front-loads the primary output (commission, with currency unit) before listing secondary metrics. Parenthetical qualifiers are used efficiently rather than in extra sentences. Slightly dense, but no sentence 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 correctly takes on the job of describing the return shape, and it lists the key fields and their units. However, it omits whether the result is a per-campaign array, whether zero-spend campaigns appear, and whether commission figures are final or estimated — details an agent needs to interpret results. Adequate but incomplete for a report-style read tool.

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%, with each of days, start_date and end_date documented including the 1–366 range and UTC date pattern. The description only adds the loose phrase 'no período' and does not clarify the precedence between days and explicit start/end dates beyond what the schema already states. Baseline 3 applies where the schema does the heavy lifting.

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?

The description names a specific resource (comissão, in centavos de BRL) scoped to a period and broken down by Meta campaign, and enumerates the accompanying metrics (pedidos, itens, GMV, spend, ROAS). An agent can tell this is the per-campaign commission report rather than a raw campaigns list. It stops short of naming a sibling to differentiate against (e.g. pixel_get_roas or pixel_get_conversions), so it is clear but not fully disambiguating.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance; the description only says what the payload contains. Nothing tells the agent how this differs in purpose from pixel_get_roas or pixel_get_conversions, which overlap on the same metrics. Usage must be inferred from the metric list alone.

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