Skip to main content
Glama

ROAS por nível

pixel_get_roas
Read-only

Calcula o ROAS (comissão ÷ spend Meta) no período, por nível (campaign/adset/ad). Inclui spend, comissão, GMV (centavos), pedidos, cliques e derivadas em basis points. Base para escalar/pausar.

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

Input Schema

NameRequiredDescriptionDefault
daysNoJanela em dias se start/end ausentes (1–366, default 30).
levelNoNível de agregação (default campaign).
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

A3.6/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 safety is covered. The description adds genuine behavioral context: the ROAS formula, the returned measures, and the non-obvious units (GMV em centavos, derivadas em basis points). It stops short of covering ordering, pagination, or behavior when no data exists in the window.

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?

Three short sentences, front-loaded with the metric definition, then the payload, then the decision context. Nearly every clause carries information; only 'Base para escalar/pausar' is soft, and it is short enough not to be wasteful.

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 enumerates the returned fields and their units, which is the most important gap to fill. Combined with readOnly annotations it is sufficient to call the tool correctly, with only minor gaps around empty-result and ordering behavior.

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 coverage is 100%, so the schema already documents all four parameters including defaults and the date pattern. The description still adds meaning by pairing 'no período' with the level enum values (campaign/adset/ad), reinforcing how the period and aggregation compose. Baseline would be 3, and the added unit/period framing nudges it slightly higher.

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 ('Calcula o ROAS') and defines the metric precisely as comissão ÷ spend Meta, plus the three supported aggregation levels. It is clearly distinguishable from metric siblings like pixel_get_commissions, though it never names an alternative 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?

'Base para escalar/pausar' implies the downstream decision context, which gives some sense of when the tool matters. However, it offers no explicit when-to-use/when-not guidance and does not steer the agent toward or away from sibling tools such as pixel_get_commissions or pixel_get_daily_trends.

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