Skip to main content
Glama

search_custom

Search Google with custom parameters like date ranges, file types, and site restrictions to find specific information using the Google Custom Search JSON API.

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
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool performs a search but doesn't cover critical aspects like authentication needs (implied by 'user_google_email' but not explained), rate limits, error handling, or the nature of the results (e.g., pagination, format). This is inadequate for a tool with 13 parameters and no annotation support.

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, efficient sentence that directly states the tool's purpose without any fluff. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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 the tool's complexity (13 parameters, no annotations, but with an output schema), the description is minimal. It covers the basic purpose but lacks context on authentication, behavioral traits, or when to use it. The presence of an output schema means the description doesn't need to explain return values, but it still falls short in other areas for a tool of this scope.

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?

The schema description coverage is 100%, meaning all parameters are well-documented in the input schema. The description adds no additional semantic information about parameters, such as examples or usage tips. According to the rules, with high schema coverage, the baseline is 3 even without param info in the description.

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 purpose as 'Performs a search using Google Custom Search JSON API,' which specifies the action (search) and the resource (Google Custom Search). However, it doesn't distinguish this from sibling tools like 'search_contacts' or 'search_docs,' which target different resources, so it's not a perfect 5.

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 guidance on when to use this tool versus alternatives. It doesn't mention any prerequisites, context for selection, or exclusions, leaving the agent to infer usage based on the tool name alone.

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/HuntsDesk/ve-gws'

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