Skip to main content
Glama

meta_ads_campaigns_enable

Resume a paused Meta Ads campaign by activating its status. Ad sets and ads remain in their current state unless separately enabled.

Instructions

Resumes a paused campaign by setting its status to ACTIVE. Ad sets and ads underneath retain their own status — if they are still PAUSED they do NOT auto-resume; call meta_ads_ad_sets_enable / meta_ads_ads_enable for those too. Returns the campaign id and new status. Reversible via rollback_apply or meta_ads_campaigns_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.
campaign_idYesCampaign ID to activate.
Behavior5/5

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

Given no annotations, the description fully discloses key behavioral traits: it only changes campaign status, children retain their status, returns campaign ID and new status, and is reversible.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise (three sentences) and front-loaded with the main action, followed by caveats and return info. It is efficient but could be slightly more structured.

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 simple resume tool with good schema, the description is thorough: explains scope, side effects, return value, and related tools. No output schema exists, but the return is described.

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 adequate parameter descriptions. The description does not add further parameter-specific details beyond what the schema provides, so it meets the baseline.

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's verb ('Resumes') and resource ('paused campaign'), and distinguishes it from siblings like meta_ads_ad_sets_enable and meta_ads_ads_enable by explicitly noting that child entities are not auto-resumed.

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?

It explicitly states when to use (resume paused campaigns), when not to use (if child ad sets/ads need enabling), and provides alternatives (calling meta_ads_ad_sets_enable and meta_ads_ads_enable). It also mentions reversibility via rollback_apply or meta_ads_campaigns_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