Skip to main content
Glama

meta_ads_ad_sets_enable

Resume a paused ad set by setting its status to ACTIVE. Parent campaign must also be ACTIVE for serving. Ads retain their own status.

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.
Behavior5/5

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

No annotations are provided, so the description carries full burden. It discloses key behaviors: the condition that parent campaign must be ACTIVE for serving, that individual ad statuses are preserved, return values (ad_set_id and new status), and reversibility. This is thorough.

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 four sentences, each providing distinct and necessary information. It is front-loaded with the main action and contains no fluff or redundancy.

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 no annotations and no output schema, the description covers purpose, preconditions, side effects, return information, and reversibility. It is complete for enabling an ad set.

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 baseline is 3. The description does not add significant meaning beyond the schema; it repeats that 'account_id' is optional and falls back to credentials (already in schema). No additional parameter guidance.

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 resumes a paused ad set by setting its status to ACTIVE. It specifies the resource (ad set) and action (enable), and distinguishes it from the sibling tool meta_ads_ad_sets_pause by mentioning reversibility.

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?

The description provides explicit guidance: when to use (to resume a paused ad set), a precondition (parent campaign must be ACTIVE), side effects (ads underneath retain status), and alternatives (reversible via rollback_apply or meta_ads_ad_sets_pause).

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