Skip to main content
Glama

meta_ads_ad_sets_pause

Pause a specific Meta Ads ad set to stop its ads from serving. The ad set's status changes to PAUSED, halting delivery while keeping ads active. Reversible via rollback or enable tool. Returns ad set ID and new status.

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?

Discloses that setting an ad set to PAUSED stops ads under it even if their own status is ACTIVE, confirms it does not affect sibling ad sets, and notes reversibility. No annotations exist, so description carries full burden; missing details on permission requirements or error conditions.

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 sentences, front-loaded with action and result, no redundant or vague phrases. Every sentence adds value (effect on ads, reversibility, return value, scope).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, description includes return of ad_set_id and new status. Adequate for a simple pause operation. Could mention idempotency or error behavior, but not essential for a lightweight, reversible action.

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 the description adds no additional meaning beyond what the schema provides (account_id optional with fallback, ad_set_id required). Baseline 3 is appropriate as schema already documents parameters.

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 the tool pauses a single ad set by setting status to PAUSED, distinguishes from sibling tools by specifying it affects only one ad set and not sibling ad sets, and contrasts with tools that pause ads or campaigns.

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?

Explicitly mentions it is reversible via rollback_apply or meta_ads_ad_sets_enable, but does not provide explicit 'when not to use' guidance or scenarios where alternative tools (like pausing individual ads) would be preferable.

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