Google Calendar MCP Server

Search Events

search_events

Find calendar events by full-text query across summaries, descriptions, and locations, with optional time range and calendar filters.

Instructions

Full-text search across event summaries, descriptions, and locations.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes	Search text
`time_max`	No	End of time range (RFC3339)
`time_min`	No	Start of time range (RFC3339)
`calendar_id`	No	Calendar ID (default: 'primary')	primary
`max_results`	No	Maximum number of events to return

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Sep 13, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose result ordering, pagination, case sensitivity, or whether results are ranked by relevance. For a search tool with zero annotation coverage, this is a notable gap.

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?

A single, well-formed sentence that front-loads the operation and scope. Every word earns its place with no redundancy.

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?

An output schema exists, so return values need not be explained. However, with no annotations and no usage guidance, the description leaves behavioral and selection context incomplete for a 5-parameter search tool.

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 all five parameters are already documented in the schema with types and formats (RFC3339, defaults). The description adds no parameter-specific meaning beyond what the schema provides, making 3 the baseline.

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?

States a specific verb (search) and resource (events) with the scope of fields searched (summaries, descriptions, locations). This clearly distinguishes it from siblings like list_events, though it does not explicitly name them.

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 vs list_events or other siblings. The description implies full-text search but does not state exclusions or alternatives, leaving the agent to infer routing.

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

Deploy Server