Skip to main content
Glama

ADS Beast

creative_fatigue_report

Read-only

Campaigns of a client with high frequency and falling CTR, ranked by how tired the creative is.

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

Input Schema

NameRequiredDescriptionDefault
client_idYes
threshold_frequencyNoMinimum frequency that counts as fatigue.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds useful analytic context — the fatigue criteria are frequency plus falling CTR and results are ranked — but it says nothing about the lookback window for 'falling', minimum data volumes, or whether campaigns with no creative data are included.

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?

A single sentence with no padding, and the key selection criteria come before the ranking clause. The metaphorical 'how tired the creative is' is slightly softer than a precise metric, but it costs little space and conveys intent.

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?

With no output schema and a read-only report tool, the description should characterize the result set and the time basis for CTR decline; it does the former implicitly via 'ranked by' but omits any period definition. Adequate to select the tool, thin for interpreting what comes back.

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%: threshold_frequency is documented with its default, while client_id is type-only. The description implies client scoping ('Campaigns of a client') and gestures at the frequency threshold ('high frequency'), but neither maps explicitly to a parameter name nor explains units or typical values.

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 names a concrete resource (campaigns of a given client), the two signals used (high frequency and falling CTR), and the ordering (ranked by creative fatigue), which is more than a restatement of the name. It stops short of an explicit verb or a differentiation from the similarly named sibling creative_fatigue_check.

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 or when-not-to-use guidance and no mention of the obvious alternative, creative_fatigue_check, even though the two names invite confusion. The agent must infer the split from names alone.

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.