Skip to main content
Glama

ADS Beast

analytics_attribution

Read-only

Time-decay multi-touch attribution for a client's campaigns: attributed conversions, attributed CPA and the lift against last click.

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": {
      "client_id": "<client_id>"
    },
    "name": "analytics_attribution"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back days.
client_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/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 that results use time-decay multi-touch attribution and include attributed conversions, attributed CPA, and lift against last click, which is useful beyond the annotations. It does not describe permissions, data freshness, or limitations, so it is solid but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

A single front-loaded sentence with no filler; the model, scope, and key outputs are packed efficiently. It could arguably use a second sentence for usage or parameter detail, but as written it is tight and every clause earns its place.

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 two-parameter read-only analytics tool with no output schema, the description names the attribution model and key returned metrics. However, it omits when to use it among many analytics siblings and leaves client_id semantics undocumented. Adequate but not fully complete.

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 coverage is 50%: days has a schema description ('Look-back days'), but client_id has none. The phrase 'for a client's campaigns' hints at client_id but does not state its format, required status, or how client filtering affects results, so the description does not compensate for the undocumented required parameter.

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 analytics method and scope ('time-decay multi-touch attribution for a client's campaigns') and names the outputs. This distinguishes it from generic summary/benchmark siblings, though it uses a noun phrase rather than an explicit verb.

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?

Provides no guidance on when to choose attribution versus analytics_summary, analytics_compare_periods, or the other analytics siblings, and gives no prerequisites or exclusions. The use case is only implied by the description itself.

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.