Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

meta_ads_ads_enable

Resume a paused ad by setting its status to ACTIVE. Ensure the parent ad set and campaign are active for the ad to serve. Returns the ad ID and new status.

Instructions

Resumes a paused ad by setting its status to ACTIVE. The parent ad set and campaign must also be ACTIVE for the ad to actually serve. Returns the ad_id and new status. Reversible via rollback_apply or meta_ads_ads_pause.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ad_idYesAd ID to activate.
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.
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.2/5.0
Behavior4/5

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

The description discloses the key behavioral constraint: the ad will only serve if parent ad set and campaign are ACTIVE. It also states the return value (ad_id and new status) and reversibility. With no annotations provided, the description carries the burden of behavioral disclosure, and it does so well. It could add more about side effects (e.g., whether it affects delivery immediately, or if there are any approval implications), 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?

The description is three sentences with no wasted words. The core action is front-loaded, followed by the critical prerequisite, then the return value and reversibility. Every sentence earns its place.

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 mutation tool with 3 parameters and no output schema, the description covers the essential context: what it does, the prerequisite for success, what it returns, and how to reverse it. It doesn't explain the full response format, but the description states it returns ad_id and new status, which is sufficient for an agent to know what to expect. The only minor gap is not mentioning potential failure modes (e.g., if the ad is already ACTIVE).

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 documents all three parameters. The description adds context for the 'reason' parameter by explaining it's stored in the journal and action_log, which is useful. However, it doesn't add much beyond the schema for ad_id and account_id. Baseline 3 is appropriate since the schema does the heavy lifting.

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 function: 'Resumes a paused ad by setting its status to ACTIVE.' It names the specific resource (ad), the action (resume/enable), and the mechanism (status set to ACTIVE). It also distinguishes itself from related siblings like meta_ads_ads_pause and meta_ads_campaigns_enable by focusing on the ad level.

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 provides clear context: the parent ad set and campaign must also be ACTIVE for the ad to actually serve. It also mentions reversibility via rollback_apply or meta_ads_ads_pause, which gives the agent guidance on related actions. However, it doesn't explicitly state when to use this tool versus alternatives like meta_ads_campaigns_enable or meta_ads_ad_sets_enable, though the ad-level focus is implied.

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