Skip to main content
Glama

meta_ads_ad_sets_pause

Pause a single Meta ad set to stop its ads from serving immediately. Reversible anytime without affecting sibling ad sets.

Instructions

Pauses a single ad set by setting its status to PAUSED. Ads under this ad set stop serving while it is PAUSED, even if their own status is ACTIVE. Lightweight, reversible via rollback_apply or meta_ads_ad_sets_enable. Returns the ad_set_id and new status. Does not affect sibling ad sets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ad_set_idYesAd set ID to pause.
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.
Behavior5/5

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

With no annotations, the description fully discloses the behavioral impact: status change to PAUSED, ads under it stop serving even if ACTIVE, reversibility, return value, and lack of effect on siblings. This is rich context beyond the schema, covering the essence of the operation.

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 three concise sentences, front-loaded with the primary action, followed by behavioral nuances and reversibility. Every sentence provides useful information without redundancy or fluff.

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?

For a tool with no annotations and no output schema, the description is remarkably complete. It covers purpose, effect, reversibility, return value, and scope. It does not explain permission requirements, but for a straightforward pause operation, the given context is sufficient for an agent to select and invoke it correctly.

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 description coverage is 100%, so the schema already documents ad_set_id and account_id. The description does not add parameter-specific semantics beyond what the schema provides, though it does mention the return value which indirectly references ad_set_id. This aligns with the baseline for high schema coverage.

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 tool pauses a single ad set by setting its status to PAUSED, which is a specific verb+resource. It distinguishes from siblings by emphasizing 'single ad set' and 'does not affect sibling ad sets,' and clarifies the cascading effect on ads.

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

Usage Guidelines4/5

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

The description implies usage context by mentioning it is lightweight and reversible via rollback_apply or meta_ads_ad_sets_enable, and contrasts with sibling ad sets. However, it does not explicitly enumerate when to use this tool versus enabling or updating ad sets, so it falls just short of a 5.

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