Skip to main content
Glama

meta_ads_ad_sets_enable

Activate a paused ad set to resume serving, provided the parent campaign is active. Ads with PAUSED status are not automatically resumed.

Instructions

Resumes a paused ad set by setting its status to ACTIVE. The parent campaign must also be ACTIVE for the ad set to actually serve. Ads underneath retain their own status — PAUSED ads do not auto-resume. Returns the ad_set_id and new status. Reversible via rollback_apply or meta_ads_ad_sets_pause.

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 activate.
Behavior4/5

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

With no annotations provided, description carries full burden. It discloses the status change, dependency on campaign active state, non-interference with ad status, and return value. Additional details like rate limits or authorization are not covered, but the core behavior is 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?

Three sentences front-loaded with the main purpose. Every sentence adds unique information without redundancy or fluff, making it efficient and easy to parse.

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?

Despite no output schema, the description states return values. It covers prerequisites, side effects, and reversibility. For a simple enable action with two parameters, this is sufficiently complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 100% coverage with descriptions for both parameters. Description adds value by explaining account_id fallback behavior and required prefix format, which enhances understanding beyond the 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 explicitly states 'Resumes a paused ad set by setting its status to ACTIVE,' clearly identifying the action (resume) and resource (ad set). It distinguishes from siblings by mentioning reversibility via meta_ads_ad_sets_pause and rollback_apply, and contrasts with similar tools like meta_ads_ads_enable and meta_ads_campaigns_enable.

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: 'The parent campaign must also be ACTIVE for the ad set to actually serve' and clarifies that 'PAUSED ads do not auto-resume.' It also notes reversibility, giving a clear context for use versus 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