Skip to main content
Glama

meta_ads_ads_pause

Pause a specific Meta ad immediately to stop its delivery. Use for controlling individual ad status without affecting other ads or ad sets.

Instructions

Pauses a single ad by setting its status to PAUSED. Lightweight; the ad stops serving immediately. Reversible via rollback_apply or meta_ads_ads_enable. Returns the ad_id and new status. Does not affect the parent ad set or sibling ads. Use for creative-level pause; use meta_ads_ad_sets_pause to stop a whole ad set.

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.
ad_idYesAd ID to pause.
Behavior4/5

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

Discloses that the ad stops immediately, is reversible, does not affect parent ad set or sibling ads, and returns ad_id and new status. Lacks permission requirements, but overall transparent.

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?

Four focused sentences, each adding value. Core action in the first sentence. No redundant or unnecessary information.

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 essential aspects: effect, scope, reversibility, return value, and differentiation from sibling tools. Output is not needed given the clarity.

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 covers 100% of parameters with descriptions. The description adds context about account_id being optional with fallback but no additional semantic detail beyond schema.

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' and the resource 'single ad', distinguishing it from sibling tools like meta_ads_ad_sets_pause and meta_ads_ads_enable. It specifies the action (setting status to PAUSED) and scope.

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 ('creative-level pause') and provides alternatives (meta_ads_ad_sets_pause for whole ad set). Also mentions reversibility via rollback_apply or meta_ads_ads_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