Skip to main content
Glama

Detalhar campanha

pixel_get_campaign_status
Read-only

Detalha UMA campanha Meta a partir do cache: status efetivo, objetivo e orçamento diário (centavos de BRL). Informe o ID externo da campanha (descubra com pixel_get_campaigns).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "campaign_id": "<campaign_id>"
    },
    "name": "pixel_get_campaign_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaign_idYesID externo da campanha Meta (TEXT).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.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 a genuine behavioral trait beyond annotations: the data comes 'a partir do cache', signalling possible staleness. It does not say how fresh the cache is or what happens for an unknown/deleted campaign ID, so it is not fully transparent.

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?

Two sentences, both load-bearing: the first defines scope and payload, the second defines the input and where to find it. The 'UMA' emphasis and the unit note (centavos de BRL) are front-loaded rather than buried.

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 does the job of describing the returned fields (status, objective, daily budget) and the ID sourcing, which is the core of what an agent needs. The 'cache' qualifier is asserted but unexplained (freshness, sync dependency via pixel_trigger_sync), leaving a small gap for a cache-backed read tool.

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 baseline is 3; the description goes beyond it by clarifying that the ID is the external Meta campaign ID and specifying how to obtain it via pixel_get_campaigns. It adds no format example (numeric vs. prefixed string), which caps it at 4.

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?

Specific verb ('Detalha') plus a precisely scoped resource ('UMA campanha Meta') and an explicit enumeration of what is returned: effective status, objective, and daily budget in BRL cents. It also names the sibling pixel_get_campaigns as the source of IDs, so an agent can distinguish single-campaign detail from campaign listing without inspecting schemas.

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?

It states the prerequisite workflow ('descubra com pixel_get_campaigns'), which is exactly the routing guidance an agent needs before calling. There is no explicit when-not guidance (e.g., which sibling to use for other per-campaign data such as ROAS or conversions), which keeps it below a 5.

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