Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

meta_ads_ad_sets_enable

Resume a paused Meta ad set by setting its status to ACTIVE. Parent campaign must be ACTIVE for delivery; ads keep their own status. Returns the ad set ID and new 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
reasonNoWhy this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.
ad_set_idYesAd set ID to activate.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.20.0
    • addedInput schema / properties / reason
      Added value: +{
+  "description": "Why this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.",
+  "maxLength": 500,
+  "type": "string"
+}
  2. Changed1 schema field changedv0.10.37
    • addedInput schema / additionalProperties
      Added value: +false
  3. Addedv0.9.12
  4. Removedv0.9.6
  5. Addedv0.9.2
  6. Removedv0.9.1
  7. Addedv1.0.5

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so well. It discloses the exact status change, the dependency on the parent campaign, that child ads are not automatically resumed, the return value, and reversibility via rollback_apply or meta_ads_ad_sets_pause. This gives the agent a clear model of side effects and recovery paths.

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 concise and well-structured: it opens with the core action, adds relevant caveats, states the return value, and ends with reversibility. Every sentence earns its place, and there is no redundant filler.

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?

For a simple mutating tool with no output schema, the description covers the action, preconditions, non-effects on child ads, return value, and reversibility. It does not describe edge-case behavior such as what happens if the ad set is already ACTIVE, but the provided guidance is strong enough for correct invocation in most scenarios.

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 description coverage is 100%, so the schema already fully documents ad_set_id, account_id, and reason. The description adds no parameter-specific semantic detail beyond what the schema provides, so the baseline of 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?

The description states a specific verb and resource: 'Resumes a paused ad set by setting its status to ACTIVE.' It also clarifies scope by distinguishing the ad set from its parent campaign and child ads, preventing confusion with sibling tools like meta_ads_campaigns_enable or meta_ads_ads_enable.

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?

The description clearly implies when to use it: when resuming a paused ad set. It provides important contextual guidance such as the parent campaign needing to be ACTIVE and that PAUSED ads will not auto-resume, but it does not explicitly name which sibling tools are alternatives or when not to use this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools