Skip to main content
Glama

meta_ads_ad_sets_pause

Pause a single ad set to stop its ads from serving. The ad set's status becomes PAUSED, halting all associated ads while leaving sibling ad sets unaffected. Reversible via enable or rollback.

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

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

No annotations present, so description covers behavioral traits: ads under ad set stop serving even if active, lightweight, reversible, returns ad_set_id and new status, no effect on siblings.

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 sentences, no redundant phrasing. Action verb first, efficient structure.

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?

Complete for a simple pause operation. Includes return value details, reversal mechanism, and scope. No output schema needed.

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% with good descriptions. The description adds minimal extra meaning beyond schema (e.g., account_id optional with fallback). 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?

Clearly states it pauses a single ad set by setting status to PAUSED, with specific verb and resource. Distinguishes from siblings like meta_ads_ad_sets_enable and meta_ads_ads_pause.

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?

Provides when to use (to pause an ad set), mentions reversibility via rollback_apply or enable, and clarifies it does not affect sibling ad sets. Lacks explicit comparison with ad-level pause but sufficient.

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