Skip to main content
Glama
BACH-AI-Tools

Google Search74 MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
API_KEYYesYour API key for Google Search74 API

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
searchA

The Google Search74 API endpoint allows users to perform a Google search query and retrieve relevant results based on the provided input. This endpoint is ideal for applications that require automated search capabilities, such as content aggregation, market research, or keyword analysis. ### Key Features: 1. Search Functionality: Execute a search query on Google and retrieve results. 2. Limit Results: Specify the maximum number of results to be returned. 3. Related Keywords: Optionally include related keywords in the response for deeper insights. ### Parameters: - query (string): The search term or keyword to query on Google. For example, "Nike". - limit (integer): The maximum number of search results to return. For example, 10. - related_keywords (boolean): A flag to include related keywords in the response. Set to true to retrieve related keywords, or false to exclude them. ### Response: The endpoint returns a structured JSON object containing: - Search Results: A list of search results, including titles, URLs, and snippets. - Related Keywords (if enabled): A list of keywords related to the search query for further exploration. This endpoint is designed to streamline search operations and provide actionable insights for applications leveraging Google search data.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion. The tool's purpose is clear and unambiguous.

Naming Consistency5/5

The single tool name 'search' is a verb, consistent with itself. There is no inconsistency to evaluate.

Tool Count4/5

One tool for a focused search server is reasonable. While it is on the low end of typical tool counts, the scope is narrow and adequately served by a single endpoint.

Completeness5/5

The tool covers the core search functionality with parameters for query, limit, and related keywords. It is complete for the stated purpose of performing Google searches.

Maintenance

ActivityInactive
ResponsivenessNo issues