Skip to main content
Glama

meta_ads_campaigns_pause

Pause a Meta Ads campaign instantly to stop ad spend. Sets campaign status to PAUSED, cascading pause to all ad sets and ads. Reversible action for immediate stop-spend situations.

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?

Discloses cascading effect on ad sets and ads, identifies the action as lightweight and reversible, and specifies return values. Despite no annotations, the description provides sufficient behavioral insight, though it omits potential errors or idempotency details.

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 that front-load the core action, explain effects, and provide usage guidance. Every sentence adds value 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?

Covers all aspects: purpose, effects, alternatives, reversibility, and return values. No missing critical information for a simple pause operation, especially given no output schema.

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 coverage is 100% and already provides clear descriptions for both parameters. The tool description adds no new meaning beyond what the schema states, so baseline score of 3 is appropriate.

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 action ('pauses a single campaign') and resource with specific verb+resource. It distinguishes from sibling tools like meta_ads_campaigns_enable and meta_ads_campaigns_update by explicitly mentioning alternatives for reversal and soft-delete.

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 advises when to use this tool ('Use for immediate stop-spend situations') and when to use an alternative ('use meta_ads_campaigns_update with status='DELETED' to soft-delete instead'). Also notes reversibility via rollback_apply or meta_ads_campaigns_enable.

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