Skip to main content
Glama
taylorwilsdon

Google Workspace MCP Server - Control Gmail, Calendar, Docs, Sheets, Slides, Chat, Forms & Drive

by taylorwilsdon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Search Custom

search_custom
Read-onlyIdempotent

Search the web with custom filters for sites, language, country, file type, date, safety, and image results. Specify how many results to return and where to start for full control.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed19 schema fields changedv1.28.0
    • removedInput schema / properties / country / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / country / type
      Added value: +"string"
    • removedInput schema / properties / date_restrict / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / date_restrict / type
      Added value: +"string"
    • removedInput schema / properties / file_type / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / file_type / type
      Added value: +"string"
    • removedInput schema / properties / language / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / language / type
      Added value: +"string"
    • removedInput schema / properties / search_type / anyOf
      Removed value: -[
-  {
-    "const": "image",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / search_type / enum
      Added value: +[
+  "image"
+]
    • addedInput schema / properties / search_type / type
      Added value: +"string"
    • removedInput schema / properties / site_search / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / site_search / type
      Added value: +"string"
    • removedInput schema / properties / site_search_filter / anyOf
      Removed value: -[
-  {
-    "enum": [
-      "e",
-      "i"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / site_search_filter / enum
      Added value: +[
+  "e",
+  "i"
+]
    • addedInput schema / properties / site_search_filter / type
      Added value: +"string"
    • removedInput schema / properties / sites / anyOf
      Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / sites / items
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / sites / type
      Added value: +"array"
  2. Addedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the main safety profile. The description adds no behavioral detail beyond what annotations provide, but it also does not contradict them.

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 with no wasted words. It is front-loaded with the core purpose and does not repeat information already present in the schema or annotations.

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?

For a tool with 13 parameters, the one-sentence description provides minimal orientation and omits practical context such as quota/auth requirements or the need for a configured Custom Search Engine. The rich schema and output schema compensate partially, but the description could be more helpful.

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%, and the schema documents all 13 parameters with descriptions and defaults. The description itself adds no parameter-level meaning, so the baseline of 3 is appropriate.

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 names a specific verb ('Performs a search') and a specific resource ('Google Custom Search JSON API'), which clearly identifies this as a web/custom search tool. It is distinct from sibling search tools like search_gmail_messages, search_drive_files, and search_docs.

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. With many sibling search tools available, an agent receives no explicit or implicit cue about when to choose Google Custom Search over Gmail, Drive, or Docs searches.

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

Deploy Server

Other Tools