google-calendar-mcp

list_events

Retrieve a list of Google Calendar events for a specified period. Filter by time range, search query, and adjust sorting, limits, and recurring event handling.

Instructions

指定した期間のカレンダーイベント一覧を取得します

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_events"
  }
}

Input Schema

Name	Required	Description	Default
`q`	No	検索クエリ
`orderBy`	No	ソート順	startTime
`timeMax`	No	取得終了日時（ISO 8601形式）
`timeMin`	No	取得開始日時（ISO 8601形式、例: 2024-01-01T00:00:00Z）
`calendarId`	No	カレンダーID	primary
`maxResults`	No	最大取得件数
`singleEvents`	No	定期イベントを個別インスタンスに展開するか

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only mentions the time period filter, but fails to disclose important behaviors like default sorting (startTime), max results, recurring event expansion (singleEvents), or default calendarId. This is insufficient for a complex listing tool.

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 that directly states the core purpose. It is concise, front-loaded, and contains no wasted words, even though it may be under-specified for other dimensions.

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?

For a tool with 7 parameters, no annotations, and no output schema, this description is incomplete. It fails to mention usage context, default behaviors, or differentiation from search_events. While the schema covers parameters, the description does not help the agent decide when to invoke it or what to expect.

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 the baseline is 3. The description adds no parameter-level meaning beyond what the schema already provides; it only paraphrases the time range that is already described in timeMin/timeMax.

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 retrieves a list of calendar events for a specified period, using a specific verb and resource. However, it does not distinguish this from the sibling tool 'search_events', which may also list events in a period.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when you need events within a date range ('指定した期間'), but it provides no explicit guidance on when to use this tool versus search_events or other sibling alternatives. No exclusions or alternative recommendations are given.

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

Deploy Server