Skip to main content
Glama

ADS Beast

analytics_growth_opportunities

Read-only

Campaigns ready to scale: ROAS well above target, CPA well below target, or budget left unused.

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

Input Schema

NameRequiredDescriptionDefault
client_idNo
min_roas_multiplierNoROAS-to-target ratio that counts as ready to scale, for example 1.5.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/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 genuine value by disclosing the inclusion logic that determines which campaigns appear in the result. It stops short of explaining what 'target' means, how results are ordered or bounded, or what the response 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short fragment with no padding, so nothing is wasted. But the terseness crosses into under-specification: there is no subject or verb, so the sentence does not read as a tool description an agent can act on without the name as a crutch.

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

Completeness2/5

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

With no output schema and one of two parameters undocumented, the description carries more burden than it meets. It never states the shape of the returned opportunities, how client_id scopes the query, or where the performance 'targets' come from, all of which an agent needs to call and interpret this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%: min_roas_multiplier is documented in the schema, but client_id is undocumented everywhere. The description does not compensate, and its phrasing 'well above target' sits in mild tension with the parameter's default 1.5 multiplier, leaving the actual threshold logic ambiguous.

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 defines the tool's output set concretely: campaigns meeting one of three scale-readiness criteria (ROAS above target, CPA below target, or unused budget). That is specific enough to distinguish it from siblings like audit_wasted_spend or analytics_kpi_health. It loses a point for being a noun fragment with no verb and for never naming what the tool actually returns.

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 guidance, no prerequisites, and no reference to alternative tools for adjacent questions (e.g. diagnosing underperformers vs scaling winners). The criteria imply a scaling-decision context, but the agent must infer that entirely.

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.