Skip to main content
Glama
DatalisHQ

ZuckerBot

by DatalisHQ

zuckerbot_get_campaign_insights

Query campaign, ad set, or ad-level performance for any Meta ad campaign, with date range, status, and name filters. Tags rows to benchmark automated campaigns against manually managed ones.

Instructions

Query campaign, ad set, or ad-level performance for any campaign in the connected Meta ad account — including campaigns not created by ZuckerBot. Tags each row with is_zuckerbot so you can benchmark ZuckerBot campaigns against manually managed ones. Supports date range filtering, campaign name search, status filters, time-series breakdowns, and multi-column sorting. For deduped truth use meta_result / cost_per_meta_result (Meta's Ads Manager "Results" for any objective) or conversion_leads / meta_leads — not the inflated, deprecated leads / cpl (the response's metric_semantics object labels every lead field). meta_result and conversion_leads are most reliable on campaign-level, non-time-incremented queries. Adset/ad rows report their OWN status — status_scope says which entity a row's status belongs to, statuses are as of status_synced_at, and refresh=true re-syncs them; spend-by-date is authoritative for whether delivery actually happened.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoOptional sort field. Plain values sort descending; prefix with '+' for ascending. One of: spend, leads, cpl, meta_leads, conversion_leads, cpcl, meta_result, cpmr, results, cpr, ctr, impressions. Prefer meta_result / cpmr (Meta's deduped 'Results' for any objective) or conversion_leads / meta_leads over the deprecated, inflated leads / cpl.
levelNoReturn campaign totals, ad set breakdowns, or ad breakdowns
limitNoMaximum campaigns to return after sorting
searchNoOptional case-insensitive campaign name substring filter
statusNoOptional status filter. Use active, paused, or all for the simple path, or pass legacy comma-separated values such as ACTIVE,PAUSED.
date_toNoOptional end date in YYYY-MM-DD format. Defaults to today.
refreshNoBypass the short-lived performance cache
date_fromNoOptional start date in YYYY-MM-DD format. Defaults to 7 days ago.
business_idNoOptional business ID override linked to the connected Meta ad account
campaign_idsNoOptional comma-separated Meta campaign IDs
time_incrementNoOptional daily or monthly time-series breakdown
Behavior4/5

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

With no annotations, the description carries full burden. It discloses that rows are tagged with is_zuckerbot for benchmarking, explains status_scope and status_synced_at, notes that spend-by-date is authoritative for delivery, and mentions cache bypass via refresh. It does not explicitly state it is read-only, but the query nature is clear. Minor omission of explicit non-destructive statement prevents a 5.

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

Conciseness4/5

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

The description is lengthy but well-structured, front-loading the core purpose and then layering details. Every sentence provides useful guidance (metric preferences, status handling, benchmarking). It could be slightly more concise by grouping related details, but the density is justified by the tool's complexity.

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?

Given 11 parameters, no output schema, and no annotations, the description covers the main aspects: purpose, filtering, sorting, metrics reliability, status interpretation, and cache behavior. It does not mention error scenarios or rate limits, but for a read-only query tool this is acceptable. The thorough metric guidance and benchmarking feature make it quite complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for all 11 parameters. The description adds significant value beyond schema by explaining preferred sort values (meta_result, conversion_leads), clarifying deprecated metrics (leads/cpl), detailing status filter behavior (simple vs legacy), and describing refresh, time_increment, and status semantics. This goes well beyond baseline schema descriptions.

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 queries campaign, ad set, or ad-level performance for any campaign in the connected Meta ad account. It specifies the resource (campaign/adset/ad-level performance) and action (query), and distinguishes from sibling tools by noting it includes campaigns not created by ZuckerBot and provides benchmarking via is_zuckerbot tag.

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 on when to use this tool (for performance queries) and includes detailed guidance on metric selection (prefer meta_result over deprecated leads) and reliability conditions (campaign-level, non-time-incremented). However, it does not explicitly contrast with sibling tools like zuckerbot_get_account_insights or zuckerbot_get_campaign, which would strengthen when-to-use guidance.

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