Skip to main content
Glama

ADS Beast

creative_fatigue_check

Checks Meta and TikTok campaigns for tired creatives now and files an alert and a change proposal for each one found. Proposals wait for a person.

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

Input Schema

NameRequiredDescriptionDefault
client_idNo
campaign_idNoADS Beast id from list_campaigns, not the platform's.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), the description discloses the concrete side effects: an alert is created and a change proposal is filed per fatigued creative, and proposals require human approval. That is exactly the context an agent needs before invoking a non-read-only tool. It still omits what threshold defines 'tired' and whether re-running creates duplicate proposals.

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?

Two short sentences, front-loaded with the action and scope, then the consequence. No filler or restatement of the title.

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 return-behavior burden and does so by naming the artifacts produced (alert, change proposal) and their approval state. What remains missing is detection criteria and duplicate-handling on repeat runs, which keeps it from being 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 only 50%: campaign_id is documented in the schema as an ADS Beast id from list_campaigns, but client_id has no description anywhere. The description mentions no parameters at all, so it does not compensate for the coverage gap or clarify the scoping relationship between client_id and campaign_id (especially given zero required parameters).

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 verb and resource ('checks Meta and TikTok campaigns for tired creatives') plus the outcome ('files an alert and a change proposal'), which is far more informative than the bare name. It does not explicitly name the sibling it differs from, so an agent must infer from 'now' that creative_fatigue_report is the non-actioning counterpart.

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 phrase 'now' hints at an on-demand/immediate check versus the reporting sibling, and 'proposals wait for a person' signals this is safe to run because nothing ships automatically. But there is no explicit when-to-use/when-not guidance and no named alternative, so the routing decision is only implied.

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.