Skip to main content
Glama

Search Custom

search_custom
Read-onlyIdempotent

Perform a custom search using Google's API with options for image, site restriction, date range, and file type.

Instructions

Performs a search using Google Custom Search JSON API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailYesThe user's Google email address. Required.
qYesThe search query. Required.
numNoNumber of results to return (1-10). Defaults to 10.
startNoThe index of the first result to return (1-based). Defaults to 1.
safeNoSafe search level. Defaults to "off".off
search_typeNoSearch for images if set to "image".
site_searchNoRestrict search to a specific site/domain.
site_search_filterNoExclude ("e") or include ("i") site_search results.
date_restrictNoRestrict results by date (e.g., "d5" for past 5 days, "m3" for past 3 months).
file_typeNoFilter by file type (e.g., "pdf", "doc").
languageNoLanguage code for results (e.g., "lang_en").
countryNoCountry code for results (e.g., "countryUS").
sitesNoList of sites/domains to restrict search to (e.g., ["example.com", "docs.example.com"]). When provided, results are limited to these sites.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, indicating it's a safe read operation. The description adds no further behavioral context such as rate limits, auth requirements, or pagination behavior. It neither contradicts nor enhances the annotations.

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 single sentence, making it very concise. However, it lacks any structural elements like bullet points or sections, and it could benefit from a brief note on the tool's purpose among siblings. Nonetheless, it is not verbose.

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?

Despite having a complex input schema with 13 parameters and an output schema, the description is minimal. It does not explain what the search returns, how to handle pagination, or any constraints on usage. The annotations provide some context, but the description fails to give a complete picture.

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 description coverage is 100%, so every parameter is documented in the input schema. The description adds no extra meaning beyond what the schema provides. It does not explain parameter interactions or provide examples.

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 it performs a search using Google Custom Search JSON API, but it doesn't differentiate from sibling search tools like search_contacts or search_docs, which also perform searches. The verb 'search' is clear but the resource is vague without specifying what is being searched (e.g., web results).

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. There are many sibling search tools, but the description provides no context about when to choose search_custom over search_docs, search_drive_files, etc. No exclusions or prerequisites are mentioned.

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/chadvdwww-hash/worksuite-mcp'

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