Skip to main content
Glama

update_event

Update an existing calendar event by sending only the fields you want to change. Uses ETag for conflict detection to prevent overwriting concurrent modifications.

Instructions

Update an existing calendar event.

Only send the fields you want to change — unchanged fields are preserved. Requires the event's ETag for optimistic concurrency; if the event was modified elsewhere, the update will fail with a conflict error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_idYesEvent ID (UID) from a previous get_events call
etagYesETag from a previous get_events call (for conflict detection)
calendarNoCalendar name or ID where the event lives
titleNoNew title (omit to keep current)
startNoNew start datetime, ISO 8601 with timezone (omit to keep current)
endNoNew end datetime, ISO 8601 with timezone (omit to keep current)
descriptionNoNew description (omit to keep current)
locationNoNew location (omit to keep current)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Discloses partial update and concurrency conflict, but lacks details on idempotency, error conditions (e.g., event not found), or rate limits. No annotations to offset.

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?

Two sentences, front-loaded with purpose, no filler. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return values not required. Covers core behavior and conflict detection. Could mention field-clearing semantics more explicitly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%. Description adds value by clarifying partial update mechanism (send only changed fields) and ETag purpose. Slightly above baseline due to helpful context.

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?

Clear verb+resource: 'Update an existing calendar event.' Distinguishes from siblings like create_event, delete_event, get_events, get_freebusy, and list_calendars.

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

Usage Guidelines4/5

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

Explicitly states partial update behavior and ETag requirement for optimistic concurrency. Provides clear guidance on usage context, though does not explicitly contrast with alternatives.

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

Install Server

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/aberhamm/ical-mcp'

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