Skip to main content
Glama

SpendCanary free Google Ads tools

Google Ads wasted spend calculator

wasted_spend_from_search_terms
Read-onlyIdempotent

Reads a Google Ads search terms report (CSV text) and totals the spend on search terms with no conversions, with the costliest ones and a monthly figure.

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": {
      "csv": "<csv>"
    },
    "name": "wasted_spend_from_search_terms"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvYesThe Google Ads search terms report exported as CSV, as text (up to 2 MB).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed operation. The description adds useful behavioral context by saying it totals spend on no-conversion terms and reports costliest terms plus a monthly figure, but it omits parsing assumptions, required CSV columns, and edge-case behavior.

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?

The description is a single front-loaded sentence with no wasted wording. It moves directly from the input action to the computed outputs.

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?

There is no output schema, so the description must carry the return-value burden. It gives a conceptual summary of outputs, costliest terms and a monthly figure, but does not specify the exact return structure or the CSV columns needed for parsing and conversion detection.

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 description coverage is 100%, so the single csv parameter is already fully documented as a Google Ads search terms report exported as CSV text up to 2 MB. The description adds no parameter meaning beyond what the schema provides, making the baseline 3 appropriate.

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 states a specific verb and resource: it reads a Google Ads search terms report CSV and totals spend on non-converting terms. It also names the computed outputs, costliest terms and a monthly figure, though it does not explicitly differentiate itself from sibling ad-metric tools.

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 implied by the description: use this when you have a search terms report CSV and want wasted spend from non-converting terms. It does not state when not to use it or name alternatives such as the sibling budget, CPC, or ROAS tools.

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.