Skip to main content
Glama

Search Custom

search_custom
Read-onlyIdempotent

Search the web via Google Custom Search, limit results to selected domains, and filter by date, language, country, or file type. Retrieve web or image results with customizable result counts.

Instructions

Performs a search using Google Custom Search JSON API.

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Install Server

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, so safety is covered by structured metadata. The description adds no behavioral context beyond the API name, such as quota usage, authentication needs, or result variability. There is no contradiction with 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 front-loaded sentence with no filler or repetition. It is concise, though slightly under-specified for a tool with 13 parameters and many sibling search tools.

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?

The output schema and annotations cover return values and safety traits, so those gaps are filled by structured data. However, the description does not clarify what kind of content search_custom searches, when to choose it over sibling search tools, or what domain-specific setup (e.g., a configured custom search engine) might be required. For a tool with 13 parameters and a large sibling set, this one-liner is not complete enough.

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, default, and constraint is already documented in the input schema. The description contributes no additional parameter meaning, but the high schema coverage means the description does not need to compensate.

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 states a clear action ('Performs a search') and identifies the specific API ('Google Custom Search JSON API'), which is distinct from sibling search tools for Gmail, Drive, Docs, and other services. It does not explicitly describe the search scope (web, sites, images), but the API name and parameter schema provide enough orientation.

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 gives no guidance on when to use this tool versus alternatives such as search_drive_files, search_gmail_messages, or search_docs. It also does not mention prerequisites, exclusions, or typical use cases. An agent must infer all usage context from the tool name and schema.

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

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/WorldCentralKitchen/google_workspace_mcp'

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