Skip to main content
Glama

Pausar campanha

pixel_pause_campaign
DestructiveIdempotent

Pausa uma campanha Meta (status PAUSED). DRY-RUN com dry_run:true (mostra o efeito sem aplicar); executa somente quando dry_run for false. Requer plano Pro para executar.

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

Input Schema

NameRequiredDescriptionDefault
dry_runNotrue ou ausente = DRY-RUN: descreve o efeito sem aplicar. false = EXECUTA a ação de fato. Só envie false após o usuário confirmar.
campaign_idYesID externo da campanha Meta.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructive/openWorld/idempotent, so safety is covered structurally; the description adds the meaningful extras — that the default is a dry-run preview, that execution is gated on dry_run=false, and that a Pro plan is required. It does not mention irreversibility or how to undo, but the dry-run contract is the key behavioral fact.

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 compact sentences with the core action front-loaded and the execution gate immediately after. No filler; the only mild redundancy is repeating the dry-run mechanic that the schema also documents.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter mutation with a fully documented schema and annotations covering safety, the description supplies everything an agent still needs: the dry-run default, the execution condition, and the plan gate. No output schema exists, but a pause action's return value is predictable from the stated effect.

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%, and the schema already explains dry_run's default and confirmation requirement in detail. The description restates the dry-run semantics at a higher level but adds no format or constraint detail for campaign_id beyond the schema, so this lands at the baseline.

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 first sentence states a specific verb and resource ("Pausa uma campanha Meta") plus the resulting status, so the agent knows exactly what the tool does. It is distinguishable from pixel_resume_campaign by the verb, though it never names that sibling explicitly.

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 gives clear operational conditions: dry_run:true previews, execution happens only when dry_run is false, and a Pro plan is required to execute. It does not discuss when to prefer this over related tools like pixel_set_budget or how to confirm with the user, but the execution gate is well spelled out.

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