Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

meta_ads_ads_pause

Pause a single Meta ad immediately by setting its status to PAUSED. Reversible, and leaves the parent ad set and sibling ads unaffected.

Instructions

Pauses a single ad by setting its status to PAUSED. Lightweight; the ad stops serving immediately. Reversible via rollback_apply or meta_ads_ads_enable. Returns the ad_id and new status. Does not affect the parent ad set or sibling ads. Use for creative-level pause; use meta_ads_ad_sets_pause to stop a whole ad set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ad_idYesAd ID to pause.
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.7/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 behavioral burden. It discloses that the operation is lightweight, immediate, reversible, scoped to a single ad, and that it returns the ad_id and new status. This goes well beyond a bare mutation statement.

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 with no filler: action, effect, reversibility, return value, scope, and alternative are each covered in one compact pass. It is front-loaded with the core action and immediately explains consequences.

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 3-parameter tool with no output schema, the description covers behavior, return value, scope, reversal, and sibling differentiation. Nothing an agent needs to invoke the tool correctly is missing.

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 documents all parameters. The description adds little parameter-specific meaning beyond what the schema provides, but it does reinforce the single-ad scope tied to ad_id and notes the return value containing ad_id. This meets the baseline for high schema coverage.

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: 'Pauses a single ad by setting its status to PAUSED.' It differentiates itself from siblings by noting it does not affect the parent ad set or sibling ads, and explicitly names the alternative meta_ads_ad_sets_pause for stopping a whole ad set.

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 gives explicit usage context: 'Use for creative-level pause; use meta_ads_ad_sets_pause to stop a whole ad set.' It also names rollback_apply and meta_ads_ads_enable as reversal paths, so an agent knows exactly when and how to use this tool versus alternatives.

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