Skip to main content
Glama

SpendCanary free Google Ads tools

Google Ads wasted spend problems on Reddit

google_ads_problem_trends
Read-onlyIdempotent

How often each Google Ads wasted spend problem (junk searches, search partners, overspending, click fraud, location targeting, Google changing the account, PMax brand spend) comes up in public Reddit posts: the last 12 weeks, or monthly per 1,000 posts since January 2025. From SpendCanary's daily count; mentions, not a sample of advertisers.

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_problem_trends"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoOne problem, or all: wasted_spend, irrelevant_terms (broad match and junk searches), partners_display (search partners and Display), overspend, click_fraud, location, auto_changes (Google changing the account), pmax_brand.all
periodNoweeks: the last 12 weeks. months: monthly rate per 1,000 posts since January 2025.weeks

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The description goes beyond the read-only/idempotent annotations by disclosing the data source (SpendCanary's daily count), the normalization method (monthly rate per 1,000 posts), and an important interpretation caveat (mentions, not a sample of advertisers). It stops short of describing the response shape or any staleness/latency of the daily count.

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?

Roughly two sentences with no filler, and the core purpose is front-loaded. The parenthetical list of problems and the trailing caveat make it dense but every element carries information.

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?

There is no output schema, so the description must convey what comes back; it does state the metric (frequency of mentions) and both time framings. It could say more about the return structure — e.g., whether results are broken out per problem — but for a zero-required-parameter, two-enum tool it is nearly sufficient.

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 100% with enum descriptions for both parameters, so the baseline is 3. The description adds interpretive value by defining the period semantics (last 12 weeks versus monthly rate per 1,000 posts since January 2025) in plain language, reinforcing what the enum labels mean.

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 specific resource and metric: how often each Google Ads wasted-spend problem appears in public Reddit posts, with two time baselines. That is concrete enough to distinguish it from computational siblings such as wasted_spend_from_search_terms or search_partners_cost, though it never explicitly contrasts itself with them.

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?

Usage is only implied — an agent can infer this is for gauging how frequently a problem is discussed, but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool for spend quantification.

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.