Skip to main content
Glama

SpendCanary free Google Ads tools

Search partners cost estimator

search_partners_cost
Read-onlyIdempotent

Compares cost per conversion on Google Search with the Search Partners network and estimates what partners cost a month beyond Search, using the same rule as the SpendCanary scan.

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": {
      "google_search_cost": "<google_search_cost>",
      "google_search_conversions": "<google_search_conversions>",
      "search_partners_cost": "<search_partners_cost>",
      "search_partners_conversions": "<search_partners_conversions>"
    },
    "name": "search_partners_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoDays the figures cover.
currencyNoCurrency code for the amounts; amounts are shown in it, never converted.USD
google_search_costYes
search_partners_costYes
google_search_conversionsYes
search_partners_conversionsYes

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, idempotentHint, non-destructive and closed-world, so the safety profile and side-effect story are fully covered. The description adds that this is an estimator reusing a known rule from the SpendCanary scan, which signals a derived/computed result rather than raw data retrieval. It does not disclose how the monthly figure is derived from the supplied period or whether partial data is tolerated.

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?

One dense sentence that front-loads the comparison and then the cost estimate, with no filler. The 'same rule as the SpendCanary scan' clause is the only part that consumes space without adding actionable information.

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?

For a six-parameter estimator with no output schema, the definition explains the headline comparison but omits the shape of the result (cost per conversion figures, delta, monthly estimate) and the period semantics linking days to the monthly projection. Annotations remove any safety concerns, so the remaining gap is interpretive rather than operational.

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?

Only 2 of 6 parameters (days and currency) carry schema descriptions, leaving the four cost/conversion inputs undocumented in both schema and description. The description never clarifies whether google_search_cost is total spend over the days window, how the monthly partner-cost estimate relates to the days parameter, or that amounts are not converted between currencies. With coverage at 33%, the description needed to compensate and does not.

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 two specific resources: it compares cost per conversion between Google Search and Search Partners, and estimates incremental monthly partner cost. The purpose is unmistakable and clearly distinct from siblings like cpc, roas, or wasted_spend_from_search_terms, though it never explicitly routes an agent away from those. The trailing clause 'using the same rule as the SpendCanary scan' adds flavor without concrete meaning.

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 by the purpose statement: an agent can infer it should call this when evaluating Search Partners efficiency versus core Search. There is no explicit when-to-use, no exclusions, no mention of prerequisites such as having Search and Partners data for the same period, and no named alternative for a pure CPC or ROAS question.

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.