Skip to main content
Glama
redesignhealth

Google Workspace MCP Server

search_custom

Run Google Custom Search to find web results with custom filters like date, file type, language, safe search, and site restriction. Returns a list of results with title, URL, and snippet.

Instructions

Performs a search using Google Custom Search JSON API.

Args: user_google_email (str): The user's Google email address. Required. q (str): The search query. Required. num (int): Number of results to return (1-10). Defaults to 10. start (int): The index of the first result to return (1-based). Defaults to 1. safe (Literal["active", "moderate", "off"]): Safe search level. Defaults to "off". search_type (Optional[Literal["image"]]): Search for images if set to "image". site_search (Optional[str]): Restrict search to a specific site/domain. site_search_filter (Optional[Literal["e", "i"]]): Exclude ("e") or include ("i") site_search results. date_restrict (Optional[str]): Restrict results by date (e.g., "d5" for past 5 days, "m3" for past 3 months). file_type (Optional[str]): Filter by file type (e.g., "pdf", "doc"). language (Optional[str]): Language code for results (e.g., "lang_en"). country (Optional[str]): Country code for results (e.g., "countryUS").

Returns: str: Formatted search results including title, link, and snippet for each result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYes
numNo
safeNooff
startNo
countryNo
languageNo
file_typeNo
search_typeNo
site_searchNo
date_restrictNo
user_google_emailYes
site_search_filterNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It does document the return format and parameter defaults, which adds value, but it omits operational constraints such as rate limits, authentication prerequisites (beyond the user email parameter), and potential errors. This makes it partially transparent but not comprehensive.

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

Conciseness4/5

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

The description is a well-structured docstring that front-loads the purpose and then systematically documents each parameter and the return value. It is appropriately sized for a 12-parameter tool, with no fluff, though it is somewhat mechanical and could benefit from a more agent-friendly summary.

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?

Given the tool's 12-parameter complexity and the presence of an output schema, the description covers all parameters and the return format adequately. It does not mention caveats, rate limits, or alternative tool selection, but it provides enough for an agent to invoke the tool correctly in a straightforward search scenario.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description compensates thoroughly. It provides detailed semantics for every parameter, including ranges (num 1-10), defaults, allowed literal values, and examples for date_restrict and language. This adds substantial meaning beyond the bare schema types and defaults.

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 identifies the tool as performing a search using the Google Custom Search JSON API, with a specific verb and resource. It does not explicitly differentiate from the sibling search_custom_siterestrict, but the general web search 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?

The description provides no explicit guidance on when to use this tool versus alternatives like search_custom_siterestrict or search_docs. It simply documents parameters and return values without any 'use when' or 'alternatives' context.

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/redesignhealth/google-mcp-unofficial'

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