Skip to main content
Glama

ADS Beast

analytics_summary

Read-only

Spend, CTR, CPA and ROAS of one client over a period. Money is reported in the account currency and never summed across currencies.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "client_id": "<client_id>"
    },
    "name": "analytics_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back days.
platformNogoogle, meta, tiktok, linkedin or microsoft.
client_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: money is reported in the account currency and is never summed across currencies. It does not say whether an omitted platform aggregates across all platforms or what happens with multi-currency accounts beyond the non-summing rule.

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?

Two sentences, zero filler, with the metric list front-loaded and the currency caveat placed second where it reads as a caveat. Nothing could be removed without losing information.

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?

With no output schema, the description usefully enumerates the four returned metrics and covers the currency edge case. However, for a three-parameter analytics tool it leaves the platform-omission behavior and the relationship to overlapping siblings unexplained, which an agent needs in order to call it correctly.

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 coverage is 67%: days and platform are documented in the schema, while client_id is not. The description reinforces the client scope and time window conceptually but adds no format or defaulting detail, and does not clarify the semantics of omitting platform. Baseline 3 is appropriate given the schema does most of the work.

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 description names the exact metric set (Spend, CTR, CPA, ROAS) and the scope (one client over a period), so an agent knows precisely what data comes back. It stops short of a clear verb and never distinguishes itself from siblings such as analytics_kpi_health, analytics_compare_periods, or campaign_dashboard_summary.

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 guidance on when to choose this over the many other analytics tools, and no stated exclusions or prerequisites. A single sentence about using compare_periods for deltas or kpi_health for health scoring would have resolved the ambiguity.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.