Skip to main content
Glama

meta_ads_ads_pause

Pause a single Meta ad immediately by setting its status to PAUSED. Stops ad serving without affecting parent ad set or sibling ads. Reversible via enable action.

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?

With no annotations, the description fully discloses behavior: lightweight, immediate effect, reversible, does not affect parent ad set or siblings, and returns ad_id and new status. It covers key traits but could mention permissions or rate limits; still very good.

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 five sentences, each adding value. It front-loads the main purpose and action, with no unnecessary words. Efficient and well-structured.

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?

Given the simplicity of the tool and lack of output schema, the description covers what the tool does, its effects, reversibility, return value, and scoping. It is complete for the intended use.

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%, so parameters are already well documented. The description adds no extra parameter details beyond what's in the schema, so baseline 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 it pauses a single ad by setting its status to PAUSED, with specific verb and resource. It distinguishes itself from sibling tools by specifying that it is for creative-level pause, while meta_ads_ad_sets_pause is for stopping a whole ad set.

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?

Provides explicit when-to-use guidance: 'Use for creative-level pause; use meta_ads_ad_sets_pause to stop a whole ad set.' Also mentions reversibility via rollback_apply or meta_ads_ads_enable, giving clear context on alternatives.

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