Skip to main content
Glama

ADS Beast

client_goals

Read-only

KPI goals (ROAS, CPA, CTR, CPC) with target, current value, progress and status. Without client_id: goals of every client.

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": "client_goals"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 one genuinely behavioral fact beyond the schema: omitting client_id fans out across all clients rather than erroring. It says nothing about volume, ordering, or pagination for that cross-client case, which is where the risk lies.

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, zero preamble, with the returned fields front-loaded and the scoping rule second. The second sentence is a bare fragment, but it is unambiguous and earns its place.

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 one optional parameter, no output schema and annotations covering read safety, the description supplies enough: what is returned (metric, target, current, progress, status) and how scope changes with the parameter. Only the cross-client result volume is left unaddressed.

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

Parameters4/5

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

Schema coverage is 0% and the schema only lists client_id as an optional integer, so the description carries the burden — and it does, explaining that client_id scopes to one client and its absence means all clients. That is the key semantic for the single parameter, though it does not say what a client_id of an unknown or unauthorized client yields.

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?

States a specific resource (KPI goals) and enumerates the metrics (ROAS, CPA, CTR, CPC) plus the fields returned (target, current value, progress, status). It is clear what the tool does, though it does not explicitly distinguish itself from look-alikes such as analytics_kpi_health or audit_conversion_goals.

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 second sentence implies the two usage modes: pass client_id for one client, omit it to get every client's goals. That is useful implicit routing, but there is no explicit when-to-use versus sibling tools and no statement of when the cross-client fan-out would be inappropriate.

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.