google-web-search

Web Search

get_v1

Get web search results, knowledge panel and related keywords Group: Web Search. Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`gl`	No		US
`hl`	No		en
`limit`	No
`query`	Yes	The search query. Supports plain keywords or full Google search syntax (Google Dorking). Common operators: `"exact phrase"`, `OR`, `-exclude`, `site:`, `inurl:`, `intitle:`, `intext:`, `filetype:`, `before:` / `after:` (`YYYY-MM-DD`), `related:`, numeric ranges (`10..50`). Example: ``` site:github.com intitle:awesome python -site:gist.github.com ```
`cursor`	No
`related_keywords`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 2, 2026

addedInput schema / properties / query / description

Added value: +"The search query. Supports plain keywords or full Google search syntax (Google Dorking).\n\nCommon operators: `\"exact phrase\"`, `OR`, `-exclude`, `site:`, `inurl:`, `intitle:`, `intext:`, `filetype:`, `before:` / `after:` (`YYYY-MM-DD`), `related:`, numeric ranges (`10..50`).\n\n**Example:**\n\n```\nsite:github.com intitle:awesome python -site:gist.github.com\n```"

removedInput schema / properties / query / title
```
Removed value: -"Search Query"
```

Changed2 schema fields changedSep 2, 2026

addedInput schema / properties / gl

Added value: +{
+  "default": "US",
+  "title": "Country code",
+  "type": "string"
+}

addedInput schema / properties / hl

Added value: +{
+  "default": "en",
+  "title": "Language code",
+  "type": "string"
+}

First observedAug 19, 2026

TDQS

C2.8/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose useful traits: the billing model (1 credit per call, $0.01 via x402/MPP, no API key required) and the return content (search results, knowledge panel, related keywords). However, it doesn't disclose the read-only nature explicitly, rate limits, or pagination behavior (the cursor parameter exists but is never mentioned). It adds genuine context beyond the schema but leaves several behavioral dimensions uncovered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and mostly efficient, but it contains a structural flaw: the 'Group: Web Search' fragment appears to be a merged group header and reads as broken text. The billing information is useful and reasonably placed, but the front-loading is imperfect — the core function statement comes first, which is good, though the awkward fragment detracts from professionalism.

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?

For a tool with 6 parameters, no annotations, no output schema, and no sibling context, the description is incomplete. An agent cannot determine the response format (no output schema and no description of return structure), the meaning of limit/cursor behavior, or how gl/hl defaults affect results. The well-documented query parameter and billing details are the only substantial coverage. This is inadequate for the tool's complexity.

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?

Schema description coverage is only 17% — only the 'query' parameter has a schema description, and it is thorough (covering Google Dorking syntax). The tool description adds minimal parameter value: it mentions 'related keywords' (mapping to related_keywords) and 'search results' (mapping to query), but says nothing about gl, hl, limit, or cursor. Given the low coverage, the description was expected to compensate and does not, leaving the cursor (pagination) and limit parameters essentially unexplained.

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 clear verb ('Get') and resource ('web search results, knowledge panel and related keywords'), which unambiguously conveys the tool's function. The title 'Web Search' reinforces this. There are no sibling tools to differentiate against, so the lack of differentiation language is not a penalty. The 'Group: Web Search' fragment is a formatting artifact but doesn't obscure the purpose.

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?

The description provides no guidance on when to use this tool versus alternatives — there are no sibling tools listed, but it also gives no exclusions, prerequisites, or context about suitable use cases. The only usage-adjacent information is billing ('Agents can pay per call ($0.01 via x402/MPP, no API key)'), which is a payment consideration, not a usage guideline. For a search tool that could be one of many, this is a gap.

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

All google-web-search 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?