Skip to main content
Glama

Listar campanhas Meta

pixel_get_campaigns
Read-only

Lista as campanhas Meta espelhadas no cache da conta (id externo, nome, status efetivo, objetivo e orçamento diário em centavos). Paginação: total/count/offset/has_more/next_offset.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMáximo de campanhas (1–100, default 50).
offsetNoDeslocamento para paginação (default 0).
statusNoFiltro de status (default all).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • 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"
  2. First observed

TDQS

A3.8/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 the safety profile is covered. The description adds behavior beyond that: it discloses that the data is a cache mirror of the account (implying possible staleness) and spells out the pagination envelope exposed in the response (total/count/offset/has_more/next_offset), which matters because there is no output schema. It stops short of saying how stale the cache can be or how to refresh it.

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 dense sentences with no filler: the resource, its cache-backed nature, the returned fields, and the pagination shape all appear up front. Every clause carries information the agent needs.

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 correctly compensates by listing returned fields and the pagination envelope, which is the essential missing structured data. For a read-only listing tool that is nearly complete; only refresh/staleness guidance and sorting behavior are absent.

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 limit, offset, and the status enum are already fully documented in the schema; baseline 3 applies. The description's mention of pagination fields is about the response, not about how to drive limit/offset, so it adds little meaning beyond the schema.

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?

Specific verb+resource: "Lista as campanhas Meta espelhadas no cache da conta" and it enumerates the returned fields (id externo, nome, status efetivo, objetivo, orçamento diário em centavos). It is clearly distinct from write-type siblings such as pixel_pause_campaign, but it never contrasts itself with the closely named pixel_get_campaign_status, leaving that distinction to be inferred.

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?

Usage is only implied by the description of what it lists; there is no explicit when-to-use or when-not-to-use statement and no alternative is named (e.g., pixel_get_campaign_status or pixel_trigger_sync for refreshing). The phrase "espelhadas no cache da conta" does hint at a precondition: results come from a local mirror, not live Meta data, which indirectly tells the agent when this source is appropriate.

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