Searchwire

Google results for a keyword

google_results

Read-only

The organic Google results for a keyword: rank, url, domain and title, with the time they were observed. $0.002 when collected earlier, $0.005 fetched live.

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": {
      "keyword": "<keyword>"
    },
    "name": "google_results"
  }
}

Input Schema

Name	Required	Description
`depth`	No	How many results. Default 10.
`source`	No	"index" = results collected earlier, "live" = fetched now, "any" (default) = collected first, live if none.
`country`	No	Two-letter country code. Default "us".
`keyword`	Yes
`language`	No	Two-letter language code; Chinese is "zh-TW" or "zh-CN". Default "en".

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 13, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations declare readOnlyHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds useful non-schema context: that results are organic, that observed-at timestamps are returned, and that pricing differs for cached vs live fetches ($0.002 vs $0.005). It does not mention rate limits or freshness guarantees, so it is strong but not exhaustive.

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 sentences, front-loaded with the resource and returned fields, then the cost model. Every clause carries information; no filler.

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?

For a read-only, schema-documented tool with no output schema, the description covers what is returned and the cost implications. It stops short of describing limits (max 100 depth, default 10) or failure modes, but nothing critical to correct invocation is missing.

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 coverage is 80% and the enum source, depth, country and language parameters are already well documented in the schema. The description's mention of cost per source mode is the only parameter-adjacent value add; it does not otherwise clarify parameter behavior. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('organic Google results for a keyword') and even enumerates the returned fields (rank, url, domain, title, time observed). An agent can distinguish this from siblings like keyword_volume or check_domains without opening the schema.

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 description implies usage (retrieve organic SERP data for a keyword) but gives no explicit when-to-use vs alternatives such as app_search or keyword_volume. The source index/live trade-off is mentioned but framed as pricing, not as a decision rule.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Searchwire tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?