Skip to main content
Glama

ADS Beast

analytics_benchmarks

Read-only

Reference CTR, CPC, CPA and ROAS ranges for a platform and niche. Benchmarks are orientation, not a verdict on one account.

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": {
      "platform": "<platform>"
    },
    "name": "analytics_benchmarks"
  }
}

Input Schema

NameRequiredDescriptionDefault
nicheNoBusiness niche or industry, in plain words.
platformYes

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 establish readOnlyHint, openWorldHint and destructiveHint=false, so safety is covered. The description usefully characterizes the output as ranges intended for orientation rather than judgement, but says nothing about data source, recency, or what happens when no benchmark exists for a niche – gaps that matter for an open-world reference tool.

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?

Two short sentences, front-loaded with the concrete metrics returned, followed by an interpretive caveat. No filler; the only mild weakness is that the caveat occupies space that could have carried sourcing or coverage detail.

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 no output schema, the description carries the burden of return values and does list the four metric families returned. For a low-complexity two-parameter lookup this is close to sufficient, missing only data-source/recency and empty-result behavior.

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 50%: 'niche' is described in the schema, while 'platform' is only an enum without prose. The description mentions both dimensions ('for a platform and niche') but adds no format, defaults, or fallback behavior when niche is omitted, so it neither compensates for nor extends the schema meaningfully.

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 ('Reference') and resource ('CTR, CPC, CPA and ROAS ranges') scoped to platform and niche. An agent can immediately tell this is a lookup of benchmark ranges rather than an account-analysis tool, though no sibling is named for contrast.

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?

The clause 'Benchmarks are orientation, not a verdict on one account' implicitly tells the agent this is a framing/context tool rather than a diagnostic, but there is no explicit when-to-use or when-not-to-use guidance, and no alternative (e.g. analytics_kpi_health or analytics_compare_periods) is pointed to.

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.