toffu

Campaign Performance (All Platforms)

query_campaign_performance

Read-only

Campaign performance across ALL connected ad platforms (Google, Meta, LinkedIn, ChatGPT, Microsoft, Reddit, TikTok, Pinterest, X, Taboola, Outbrain, DV360, CM360, Teads, KWAY, RTB House), merged into one normalized table.

Input Schema

Name	Required	Description	Default
`level`	No	"campaign", "adset" or "ad" (adset/ad: Meta only).	campaign
`end_date`	Yes	YYYY-MM-DD
`platforms`	No	subset of [google_ads, meta_ads, linkedin_ads, openai_ads, bing_ads, reddit_ads, tiktok_ads, pinterest_ads, twitter_ads, taboola, outbrain, dv360, cm360, teads, kway, rtbhouse]. Omit for all connected.
`breakdowns`	No	Meta delivery breakdowns, e.g. ["age"], ["gender"], ["publisher_platform", "platform_position"]. Each adds a column and splits rows.
`start_date`	Yes	YYYY-MM-DD
`account_ids`	No	per-platform account id override, e.g. {"google_ads": "1234567890"}. Picks one account in a multi-account company. On an agency, a platform connected only in client workspaces is read from every client (rows tagged _client_company_name) unless this id picks one.
`time_increment`	No	"all_days", "1" (daily) or "7" (7-day periods from start_date). LinkedIn stays whole-range.	all_days
`conversion_events`	No	Meta action types to count as conversions, summed (e.g. ["lead"], ["offsite_conversion.fb_pixel_custom"]). Default: purchases. Pick from a prior call's conversions_by_action; never list overlapping variants of one event.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

changedInput schema / properties / account_ids / description

Previous value: -"per-platform account id override, e.g. {\"google_ads\": \"1234567890\"}. Needed only for multi-account companies."New value: +"per-platform account id override, e.g. {\"google_ads\": \"1234567890\"}. Picks one account in a multi-account company. On an agency, a platform connected only in client workspaces is read from every client (rows tagged _client_company_name) unless this id picks one."

Changed1 schema field changedOct 25, 2026

changedInput schema / properties / platforms / description

Previous value: -"subset of [google_ads, meta_ads, linkedin_ads, openai_ads, bing_ads, reddit_ads, tiktok_ads]. Omit for all connected."New value: +"subset of [google_ads, meta_ads, linkedin_ads, openai_ads, bing_ads, reddit_ads, tiktok_ads, pinterest_ads, twitter_ads, taboola, outbrain, dv360, cm360, teads, kway, rtbhouse]. Omit for all connected."

Changed2 schema fields changedOct 14, 2026

addedInput schema / properties / breakdowns

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Meta delivery breakdowns, e.g. [\"age\"], [\"gender\"], [\"publisher_platform\", \"platform_position\"]. Each adds a column and splits rows."
+}

changedInput schema / properties / level / description

Previous value: -"\"campaign\" or \"adset\" (adset: Meta only)."New value: +"\"campaign\", \"adset\" or \"ad\" (adset/ad: Meta only)."

Changed1 schema field changedOct 5, 2026

changedInput schema / properties / platforms / description

Previous value: -"subset of [google_ads, meta_ads, linkedin_ads, openai_ads]. Omit for all connected."New value: +"subset of [google_ads, meta_ads, linkedin_ads, openai_ads, bing_ads, reddit_ads, tiktok_ads]. Omit for all connected."

First observedOct 2, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds genuinely useful context that results are merged and normalized across heterogeneous platforms into one table, but says nothing about latency, row volumes, or partial-connection behavior.

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?

One front-loaded sentence with the key fact (all platforms, normalized table) stated first. The 16-name platform enumeration partially duplicates the schema's platform id list, which is mild bloat, but it does signal full coverage at a glance.

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?

With an output schema present, rich 100%-covered input schema, and safety annotations, the description doesn't need to explain return values or field meanings. The remaining gap is routing guidance versus sibling reporting tools, which is a minor omission for a read-only query.

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% and every parameter is documented in the schema, so the schema carries the semantics. The description adds no parameter-level meaning beyond noting the cross-platform merge; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

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

States a specific resource and scope: campaign performance across all connected ad platforms merged into one normalized table. It's clear what it returns, but it doesn't contrast itself with nearby reporting siblings like creative_report or account_health, so an agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use, when-not-to-use, or alternative named. The 'ALL platforms' emphasis implies it is the broad reporting call, but the description never says when to prefer creative_report or account_health instead.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All toffu tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.