Skip to main content
Glama
Sign In
Meta Ads MCP

Meta Ads MCP

by AbnerZx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ads_pause_ad

Pause a single ad to stop its delivery and prevent further spend, giving you quick control over campaign performance.

Instructions

Pause a single ad.

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": {
      "ad_id": "<ad_id>"
    },
    "name": "ads_pause_ad"
  }
}

Input Schema

NameRequiredDescriptionDefault
ad_idYes
confirmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'Pause a single ad,' which merely restates the core action. It does not disclose side effects, the need for confirmation (despite a 'confirm' parameter in the schema), or what happens to the ad's status.

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?

The description is a single clear sentence with no wasted words. It is front-loaded with the action and resource. However, it may be under-specified given the tool's simplicity and missing parameter info, but conciseness itself is strong.

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

Completeness2/5

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

The tool has no annotations, no output schema, and two parameters with zero schema descriptions. The description does not explain the purpose of the confirm flag, how to identify an ad, or what response to expect. For a mutation tool with safety considerations (pausing), this is incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description mentions no parameters. The schema shows ad_id (required) and confirm (optional boolean), but the description does not explain what these mean, what format ad_id should be, or the role of confirm. The agent is left with no semantic hints beyond type/name.

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 'Pause a single ad' uses a specific verb ('pause') and resource ('ad'), clearly distinguishing it from sibling tools like ads_pause_campaign and ads_pause_adset. The qualifier 'single' reinforces that it operates on one ad at a time.

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

Usage Guidelines2/5

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

No usage guidance is provided. The description does not mention when to use this tool over alternatives (e.g., pausing a campaign or adset), nor does it mention the confirm parameter or any prerequisites. Context must be inferred entirely from the tool name.

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

Deploy Server

Other Tools