Skip to main content
Glama
DatalisHQ

ZuckerBot

by DatalisHQ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

zuckerbot_pause_campaign

Pause delivery at any level: a whole campaign (default), one ad set, or one ad — set entity_level and pass the matching id.

Instructions

Pause delivery at any level: a whole campaign (default), one ad set, or one ad — set entity_level and pass the matching id. Pausing stops delivery and spend immediately while leaving the object in Meta, and the response reports the prior status. Use adset/ad level to stop an underperformer WITHOUT killing the winners in the same campaign. To resume a reviewed Meta object, use zuckerbot_resume_campaign with its real Meta IDs and a fresh preview.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNoPause the campaignpause
entity_idNoNumeric Meta ad set or ad ID (required when entity_level is adset or ad)
business_idNoBusiness owning a spec-built campaign; use when several businesses are connected
campaign_idNoZuckerBot campaign ID or real Meta campaign ID (required when entity_level is campaign)
entity_levelNoWhat to pause: the whole campaign, one ad set, or one adcampaign

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.10
    • addedInput schema / properties / business_id
      Added value: +{
+  "description": "Business owning a spec-built campaign; use when several businesses are connected",
+  "format": "uuid",
+  "type": "string"
+}
    • changedInput schema / properties / campaign_id / description
      Previous value: -"ZuckerBot campaign ID (required when entity_level is campaign — the default)"New value: +"ZuckerBot campaign ID or real Meta campaign ID (required when entity_level is campaign)"
  2. First observedv0.4.4

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations present, the description carries the full burden and does so well: it discloses that pausing stops delivery and spend immediately, leaves the object in Meta, and reports the prior status. These are the key behavioral side effects an agent needs to know before invoking a mutating tool.

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?

Three sentences, each earning its place: mechanism, behavioral consequence, and alternative-tool routing. The information is front-loaded and no annotation details are redundantly repeated.

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 mutating tool with no output schema and no annotations, it covers all essential operational facts: supported levels, default, required ID matching, immediate effect, and the resume path. Error behavior is not described, but the call decisions an agent needs are complete.

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 each parameter and conditional requirement. The description adds the 'matching id' dependency and clarifies real Meta IDs vs ZuckerBot IDs, but the schema already carries most of the parameter semantics.

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 opening sentence states the exact operation ('Pause delivery'), the resources it applies to (campaign, ad set, ad), and the default level. It clearly distinguishes from sibling tools like zuckerbot_resume_campaign and maps directly to the entity_level enum.

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 says when to use adset/ad level ('stop an underperformer WITHOUT killing the winners') and when to use the sibling resume tool instead. This is concrete when/alternative guidance rather than implied usage.

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