Skip to main content
Glama
fvanevski

Google Search MCP Server

by fvanevski

google_search

Search the web using Google Programmable Search. Get structured results including URL, title, and snippet. Filter by date, site, language, file type, and more.

Instructions

Performs a Google Programmable Search (CSE) query. Returns a JSON list of results, each containing a URL, title, snippet, and pagemap.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe search query.
numNoNumber of results to return (1-10).
startNoThe starting index of the results (1-based). For example, `&start=11` would start at the 11th result.
dateRestrictNoRestricts results to a time period. Format: `d[number]`, `w[number]`, `m[number]`, `y[number]` (days, weeks, months, years). Example: `d7` for the last 7 days.
siteSearchNoRestricts results to a specific site. Example: `wikipedia.org`.
siteSearchFilterNoWhether to include (`i`) or exclude (`e`) results from the `siteSearch` domain.
exactTermsNoA phrase that all search results must contain. Example: "climate change"
excludeTermsNoA word or phrase that should not appear in any search results. Example: `politics`
fileTypeNoRestricts results to files of a specific extension. Example: `pdf`
glNoGeolocation of the end user. A two-letter country code. Example: `us` for United States.
lrNoRestricts the search to documents written in a particular language. Example: `lang_en` for English.
safeNoSearch safety level. `active` or `off`.active
searchTypeNoSpecifies the search type. Set to `image` for image search.
sortNoSorts results by a specific attribute. Format: `TYPE-NAME:DIRECTION`. Example: `metatags-pubdate:d` to sort by publication date in descending order.
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only mentions the return format but does not address rate limits, authentication, potential side effects, or any other behavioral characteristics. The description is minimal.

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 a single sentence that directly conveys the tool's function and output. No unnecessary words. It is appropriately concise and front-loaded.

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?

Given 14 parameters and no output schema, the description only minimally covers return values. It mentions the fields but lacks detail on pagination, error handling, or common usage patterns. Completeness is adequate but not thorough.

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 100%, so baseline is 3. The description does not add any meaning beyond what the input schema already provides; it only states the overall purpose. No parameter details are given in the description.

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?

The description clearly states 'Performs a Google Programmable Search (CSE) query' and specifies the return format (JSON list with URL, title, snippet, pagemap). There are no sibling tools to differentiate from, but the purpose is unambiguous.

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?

No guidance on when to use this tool versus alternatives or under what circumstances. Since there are no sibling tools, the lack of context still leaves the agent without information about appropriate use cases or limitations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fvanevski/google_search_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server