google-calendar-mcp

create_event

Create new Google Calendar events with start/end times, location, attendees, reminders, and recurrence rules. Supports all-day and timed events.

Instructions

新しいカレンダーイベントを作成します。定期イベントの作成も可能です

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "summary": "<summary>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "create_event"
  }
}

Input Schema

Name	Required	Description	Default
`end`	Yes	終了日時
`start`	Yes	開始日時
`colorId`	No	イベントの色ID
`summary`	Yes	イベントタイトル
`location`	No	場所
`attendees`	No	参加者リスト
`reminders`	No	リマインダー設定
`calendarId`	No	カレンダーID	primary
`recurrence`	No	繰り返しルール（RRULE形式、例: ["RRULE:FREQ=WEEKLY;COUNT=10"]）
`visibility`	No	公開設定
`description`	No	イベントの説明
`transparency`	No	予定あり(opaque)/予定なし(transparent)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The description states it creates events and supports recurring events, but with no annotations provided, it does not disclose potential side effects such as sending invitations, required permissions, or how the created event is returned. The 'creates' verb indicates mutation, but richer behavioral context is absent.

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 two short sentences, front-loaded with the main purpose and then a key extension (recurring events). No fluff or redundancy; every word contributes value.

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?

While the schema is rich and covers parameters, the description is thin given the tool's complexity (12 params, nested objects, no output schema). It does not mention return values, error behavior, or usage specifics like all-day vs timed events, leaving the agent without guidance except what the schema already provides.

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?

All 12 parameters are fully documented in the schema, including descriptions for each, so the schema covers parameter semantics. The description adds nothing beyond mentioning recurring events, which relates to the recurrence parameter but does not add new meaning.

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 clearly states the action ('create') and resource ('calendar event'), and also highlights the capability to create recurring events. This distinguishes it from sibling tools like update_event and delete_event.

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 for creating new calendar events, including recurring ones, but does not explicitly state when to use this tool versus alternatives or provide any exclusions. Guidance is minimal but not misleading.

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

Deploy Server