Skip to main content
Glama

Google Ads ad fatigue

google_ads_get_fatigue
Read-only

Google Ads campaign fatigue: CTR/CPA/ROAS decay vs the prior equal window.

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

Input Schema

NameRequiredDescriptionDefault
urlNo
daysNo
limitNo
actionNo
statusNo
date_toNo
page_idNo
sort_byNo
user_idNo
site_urlNo
client_idNo
date_fromNo
ad_accountNo
ig_user_idNo
user_emailNo
range_presetNo
activity_onlyNo
campaign_nameNo
property_nameNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / action
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Action"
      +}
    • addedInput schema / properties / status
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Status"
      +}
  2. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral information in stating that the decay is computed against a prior equal window, which tells the agent how the numbers are derived. It says nothing about thresholds, output shape, or what counts as fatigue.

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 dense sentence with the metric set and comparison window front-loaded; no filler. It is appropriately sized for what it attempts, though that attempt is far too small for the surface area of the tool.

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?

An output schema exists, so return values needn't be explained. But a 19-parameter, zero-required tool with 0% schema coverage needs the description to disambiguate the query surface, and it supplies none of that. The description is complete only about the analytical concept, not the invocation.

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

Parameters1/5

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

There are 19 parameters with 0% schema description coverage and no enums, and the description mentions none of them. Ambiguous names like 'action', 'status', 'range_preset', 'activity_only', 'url' vs 'site_url', and 'page_id' vs 'campaign_name' are left entirely undefined, so the agent has no basis for populating this schema.

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?

Names the resource (Google Ads campaign fatigue) and the specific measurement it performs: CTR/CPA/ROAS decay against the prior equal window. That is a concrete verb+resource statement an agent can act on. It stops short of differentiating itself from meta_ads_get_fatigue or meta_insights_get_fatigue beyond the platform implied by the name.

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?

Nothing says when to reach for this tool rather than google_ads_get_trends, google_ads_get_summary, or the Meta fatigue variants. The 'prior equal window' clause hints at the comparison basis but is not framed as a usage condition or an alternative-routing rule.

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.