A
licenseA
qualityD
maintenanceProvides real-time Google search results (organic + knowledge graph) with country targeting, language, time filters, and pagination, at low cost.
1
8
MIT
google-web-search
by com.jojapi
Server Details
Google Web Search: Google Web Search API. Search the world’s information, including webpages.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
TDQS
B3.3/5.0
Disambiguation5/5
With only one tool available, there is no possibility of confusing it with other tools. The tool's purpose is unambiguous because it is the sole entry point for web search.
Naming Consistency3/5
The name 'get_v1' is readable but does not follow a clear verb_noun pattern and lacks a descriptive noun like 'search_results'. Since there is only one tool, there is no internal inconsistency, but the name is vague and version-based.
Tool Count2/5
A single tool is too few for a server that purports to offer web search capabilities. Users may expect additional supporting tools (e.g., pagination, search options) rather than a single monolithic call.
Completeness4/5
The tool covers the core search operation and bundles related outputs (knowledge panel, related keywords), which addresses the primary domain need. Minor gaps like pagination or parameterized search modes are not evident but could be workaround-able.
Available Tools
1 toolget_v1Web SearchBInspect
Get web search results, knowledge panel and related keywords Billing per call: 1 Credits. Agents can pay per call ($0.01 via x402/MPP, no API key).
ParametersJSON 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 |
TDQS
B3.2/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 burden of behavioral disclosure. It discloses important business behavior: billing per call, cost, payment method, and lack of API key requirement. However, it does not disclose rate limits, error behavior, or whether results are returned in a particular format, which would be useful for agents.
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 highly concise: one sentence for purpose and one sentence for billing. It front-loads the core action and then provides essential cost/payment information. There is no filler or redundant repetition of schema details.
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?
The tool has 6 parameters, no output schema, and no annotations, yet the description only covers billing and vaguely mentions result content. Key gaps include pagination via cursor, limit semantics, country/language code behavior, and what the actual response structure looks like. This is not enough context for an agent to confidently invoke the tool in varied scenarios.
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%, so the description must compensate, but it does not. It mentions 'related keywords' as an output, which hints at the related_keywords parameter, but it does not explain cursor, gl, hl, or limit beyond what the schema titles already convey. The query parameter is well described in the schema, but the tool description itself adds little parameter-level insight.
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 clearly states the tool's function with a specific verb and resource: 'Get web search results, knowledge panel and related keywords.' It is unambiguous and matches the title 'Web Search.' Since there are no sibling tools to differentiate from, the lack of explicit sibling comparison is not a significant weakness.
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 does not explicitly state when to use this tool vs alternatives, but there are no sibling tools provided. It offers useful context about invocation: agents can pay per call ($0.01 via x402/MPP, no API key). However, usage guidance is mostly implied rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
- Changed
get_v12 fields changed- added
Input schema / properties / query / descriptionAdded 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```" - removed
Input schema / properties / query / titleRemoved value: -"Search Query"
1 tool update
- Changed
get_v12 fields changed- added
Input schema / properties / glAdded value: +{ + "default": "US", + "title": "Country code", + "type": "string" +} - added
Input schema / properties / hlAdded value: +{ + "default": "en", + "title": "Language code", + "type": "string" +}
1 tool update
- First observed
get_v1
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity – fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge – works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge – works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
google search: google web search api, web, images, videos, news, music, favicon, proxy, audio.
Search Google straight from your AI agent. Web results, images, videos, news, products, scholarly ar
GoogleSearch API: Fetch real-time Google Search results including title, links Ideal for serp api.
Search the web, images, videos, news, and local businesses with robust filters, freshness controls…
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables Google search functionality through the Google Custom Search API with enterprise-grade security authentication. Supports streamable HTTP transport protocol for real-time search operations with configurable result limits.MIT
- FlicenseBqualityDmaintenanceEnables web searching and content scraping through Google Custom Search API. Provides tools to search the internet, extract webpage content, and automatically scrape search results for comprehensive information gathering.3-
- AlicenseNot gradedqualityDmaintenanceEnables free web searching using Google search results without the need for API keys or authentication. It returns structured data including titles, URLs, and descriptions with configurable result limits.14MIT