agent1st-ads-mcp

pause_meta_campaign

Stop spending on a live Meta campaign immediately while preserving campaign settings. Use to temporarily halt ad delivery and budget allocation.

Instructions

Pause a live Meta campaign to stop all spending immediately. Campaign and settings are preserved — use enable_meta_campaign to resume. Requires Starter plan or higher.

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": "pause_meta_campaign"
  }
}

Input Schema

Name	Required	Description	Default
`campaign_id`	Yes	Meta campaign ID to pause.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Mar 22, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses key behavioral traits: the immediate spending stop, preservation of campaign and settings, and the plan requirement. However, it doesn't mention error conditions, rate limits, or authentication needs, leaving some gaps.

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 concise sentences with zero waste: first states purpose and immediate effect, second clarifies preservation and alternative tool, third specifies plan requirement. Every sentence adds essential information.

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 single-parameter mutation tool with no annotations and no output schema, the description provides good coverage: purpose, immediate effect, state preservation, alternative tool, and plan requirement. It doesn't describe return values or error cases, but given the simplicity, it's mostly complete.

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 the schema already documents the single parameter. The description doesn't add any parameter-specific information beyond what's in the schema, meeting the baseline for high schema coverage.

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?

The description clearly states the specific action ('pause'), target resource ('live Meta campaign'), and immediate effect ('stop all spending immediately'). It distinguishes from sibling tools like enable_meta_campaign and pause_tiktok_campaign by specifying the platform and action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use this tool ('pause a live Meta campaign') and when to use an alternative ('use enable_meta_campaign to resume'). Also specifies prerequisites ('Requires Starter plan or higher'), providing clear guidance on usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server