Skip to main content
Glama

ADS Beast

analytics_portfolio

Read-only

Cross-client analysis of the whole portfolio: best and worst performers, platform trends, total spend. Takes up to a minute. AI: 1 AI request.

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_portfolio"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, so safety is covered. The description adds genuinely useful non-annotation context — expected latency ('up to a minute') and cost ('1 AI request') — but says nothing about data freshness, scope of clients covered, or what happens when the portfolio is large.

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?

Three short sentences, front-loaded with the core purpose before the latency and cost notes. No padding, though the telegraphic fragment 'AI: 1 AI request' is slightly cryptic compared to plain prose.

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?

For a zero-required-parameter, read-only aggregation tool with annotations covering safety and no output schema, the description does the essential job: it states scope and enumerates the return contents. Missing only explicit routing guidance versus the many analytics_* siblings.

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 both parameters (days, platform) are fully documented structurally. The description adds no meaning beyond the schema — it never clarifies how a platform filter interacts with 'whole portfolio' analysis or how the default 30-day lookback affects results. 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?

Names a specific verb+resource ('Cross-client analysis of the whole portfolio') and enumerates the outputs: best/worst performers, platform trends, total spend. The 'cross-client'/'whole portfolio' framing separates it from single-client summary tools, though it does not name any sibling 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 by the phrase 'whole portfolio' — the agent can infer this is the all-clients overview rather than a per-client or per-campaign analysis. There is no explicit when-to-use/when-not guidance or pointer to alternatives such as analytics_summary or analytics_cross_client_insights.

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.