Skip to main content
Glama
DatalisHQ

ZuckerBot

by DatalisHQ

zuckerbot_activate_campaign

Activates an intelligence campaign using its ID, with optional overrides for page, access token, and ad account.

Instructions

Temporarily unavailable during Dealify launch hardening. Intelligence campaigns are planning-only; create a legacy-mode draft and use zuckerbot_launch_campaign for the supported live path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tier_namesNoOptional subset of approved tiers to activate
campaign_idYesIntelligence campaign ID
meta_page_idNoOptional Facebook Page ID override
meta_access_tokenNoOptional Meta/Facebook access token override
meta_ad_account_idNoOptional Meta ad account ID override (format: act_XXXXX)
Behavior1/5

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

No behavioral traits are disclosed—no side effects, permissions, or return behaviors are mentioned. The description does not compensate for the lack of annotations.

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

Conciseness3/5

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

The description is concise but serves as a status notice rather than a tool description. It front-loads the unavailability message but is not informative about the tool itself.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an unavailable tool, the description omits what the tool normally does, its return value, and how it relates to sibling tools beyond the alternative. Incomplete for understanding the tool's intended function.

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?

The description adds no parameter-level information, but the input schema has 100% description coverage, 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.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description does not state what the tool does; it only declares it is temporarily unavailable and provides an alternative. The core function of 'activate_campaign' is never explained, leaving the purpose unclear.

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 explicitly tells the agent not to use this tool due to unavailability and directs to use zuckerbot_launch_campaign instead, providing clear when-not-to-use and an alternative.

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/DatalisHQ/zuckerbot'

If you have feedback or need assistance with the MCP directory API, please join our Discord server