Skip to main content
Glama

ADS Beast

analytics_cross_client_insights

Read-only

Patterns and anomalies across clients: platforms that sag for most of them, shared niche problems, who outperforms.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "analytics_cross_client_insights"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 the safety profile is covered. The description adds scope context (cross-client aggregation, anomaly detection) but says nothing about how many clients must be present, how anomalies are defined, or what the result looks like.

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?

A single front-loaded sentence with no filler, and the three output themes are listed compactly. The telegraphic phrasing ('platforms that sag for most of them', 'who outperforms') is slightly informal but still clear.

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?

For a read-only analytical tool with no output schema, the description covers what is analyzed but not the shape or granularity of the response (per-platform rows? ranked client list?). It is adequate but leaves an agent guessing about the result before calling.

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 100%, with 'days' documented as look-back days and 'platform' listing the accepted values, so the schema does the heavy lifting. The description adds no parameter meaning of its own, which meets the baseline of 3.

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 resource ('cross-client insights') and enumerates the concrete outputs: platform-level sag across clients, shared niche problems, and relative outperformers. That 'across clients' framing distinguishes it from single-client tools like analytics_summary or client_overview, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the portfolio-level pattern-finding tool rather than a per-client report. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g., analytics_benchmarks or analytics_portfolio) to route against.

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.