Skip to main content
Glama

toffu

by ai.toffu
OverviewDiscussionsAdmin

Campaign Performance (All Platforms)

query_campaign_performance
Read-only

Campaign performance across ALL connected ad platforms (Google, Meta, LinkedIn, ChatGPT, Microsoft, Reddit, TikTok Ads), merged into one normalized table.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
levelNo"campaign", "adset" or "ad" (adset/ad: Meta only).campaign
end_dateYesYYYY-MM-DD
platformsNosubset of [google_ads, meta_ads, linkedin_ads, openai_ads, bing_ads, reddit_ads, tiktok_ads]. Omit for all connected.
breakdownsNoMeta delivery breakdowns, e.g. ["age"], ["gender"], ["publisher_platform", "platform_position"]. Each adds a column and splits rows.
start_dateYesYYYY-MM-DD
account_idsNoper-platform account id override, e.g. {"google_ads": "1234567890"}. Needed only for multi-account companies.
time_incrementNo"all_days", "1" (daily) or "7" (7-day periods from start_date). LinkedIn stays whole-range.all_days
conversion_eventsNoMeta 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

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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)."
  2. Changed1 schema field changed
    • 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."
  3. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine context by stating results are merged and normalized across platforms, but it says nothing about coverage gaps (e.g. breakdown/level restrictions to Meta, LinkedIn's whole-range behavior) or latency/cost of querying all platforms at once.

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?

A single front-loaded sentence with no filler; the platform list and the merged-table outcome are stated compactly without redundancy.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and annotations carry the safety profile. Still, for an 8-parameter cross-platform query tool with subtle platform-specific behavior (Meta-only breakdowns/levels, LinkedIn ignoring time_increment), the description omits any operational caveats an agent would need to call it well.

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 every parameter (level, platforms, breakdowns, time_increment, conversion_events, account_ids) is already documented in the schema. The description adds the 'omit all connected' framing for the platform scope but no new syntax or format detail, so the 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?

The sentence names a specific resource (campaign performance) and an explicit scope (all connected platforms, merged into one normalized table), which is far more informative than a restated title. It does not, however, differentiate itself from siblings like account_health or creative_report, so an agent gets no explicit routing signal.

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 when-to-use, when-not-to-use, or alternative-tool guidance anywhere in the description. The agent must infer from the name alone that this is the cross-platform performance reporting tool.

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

All toffu toolsInspect
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.

Resources