Skip to main content
Glama

meta_ads_campaigns_pause

Pause a Meta Ads campaign to immediately halt ad spend. Cascades to ad sets and ads; reversible via re-enable.

Instructions

Pauses a single campaign by setting its status to PAUSED. Cascades to active ad sets and ads — nothing underneath the campaign will serve while it is PAUSED. Lightweight and reversible via rollback_apply or meta_ads_campaigns_enable. Returns the campaign id and new status. Use for immediate stop-spend situations; use meta_ads_campaigns_update with status='DELETED' to soft-delete instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idNoMeta Ads account ID in the format 'act_XXXXXXXXXX' (e.g. 'act_1234567890'). Optional — falls back to META_ADS_ACCOUNT_ID from the configured credentials. The leading 'act_' prefix is required.
campaign_idYesCampaign ID to pause.
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses the cascading effect on ad sets and ads, reversibility, and the return value. It does not cover permissions or API rate limits, but the core side effects and recovery paths are clearly stated.

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?

The description is concise and front-loaded: the first sentence states the primary action, followed by the cascade behavior, reversibility, return value, and usage alternatives. Every sentence contributes useful information without redundancy.

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?

The tool is simple (two params, one required) and has no output schema, but the description covers what happens on execution, what is returned, how to reverse it, and when to use it versus the alternative. The context is complete for an agent to select and invoke the tool confidently.

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?

The input schema already provides 100% coverage for both parameters, including a detailed account_id description. The tool description adds no extra parameter-level detail beyond the fact that campaign_id is the target, so the schema carries the semantic weight.

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 verb ('Pauses'), the resource ('a single campaign'), and the exact mechanism ('setting its status to PAUSED'). It also distinguishes itself from sibling tools by noting the cascade to ad sets and ads and by contrasting with the soft-delete alternative.

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?

The description explicitly says 'Use for immediate stop-spend situations' and recommends meta_ads_campaigns_update with status='DELETED' for soft-deletion. It also names reversible paths (rollback_apply or meta_ads_campaigns_enable), giving the agent clear when-to-use and when-not-to-use guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/logly/mureo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server