Skip to main content
Glama

Reativar campanha

pixel_resume_campaign
DestructiveIdempotent

Reativa uma campanha Meta (status ACTIVE). DRY-RUN por padrão; executa só com dry_run: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_resume_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 declare destructiveHint=true, idempotentHint=true, openWorldHint=true and readOnlyHint=false. The description adds context annotations cannot convey: that the operation is dry-run by default and gated behind a Pro plan, which is exactly the kind of pre-call context an agent needs. Return payload and post-execution state are not described, keeping it at 4.

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?

Three short clauses with zero filler; the effect, the dry-run default, and the plan requirement are all front-loaded. Nothing could be removed without losing information an 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?

For a two-parameter destructive mutation, annotations plus 100% schema coverage plus the explicit dry-run/plan notes cover nearly everything an agent needs before calling. Only the failure behavior when the Pro plan is absent is left unstated.

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 spells out the dry_run default and the confirmation requirement, so the description repeats rather than extends that. campaign_id is not elaborated on beyond 'ID externo', leaving the schema to carry the load.

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 + resource + resulting state: 'Reativa uma campanha Meta (status ACTIVE)', which tells an agent exactly what mutation occurs. It does not explicitly name the sibling it inverts (pixel_pause_campaign), but the meaning is unambiguous given the sibling list.

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?

Gives clear operating context: dry-run by default, real execution only with dry_run:false, and a Pro-plan prerequisite for execution. It stops short of naming pixel_pause_campaign as the opposite action or stating when reactivation is appropriate versus other levers like pixel_set_budget.

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