Skip to main content
Glama

manage-event

Destructive

Update, decline, cancel, or delete existing Outlook calendar events. Use dry-run preview to test updates before applying them.

Instructions

Manage an existing calendar event (destructive: covers update/decline/cancel/delete — use dryRun where supported to preview). action=update edits fields in place via PATCH (subject, start, end, attendees, body, location, isOnlineMeeting, sensitivity, showAs, importance, categories, reminderMinutesBeforeStart) — only fields you pass are changed; pass dryRun: true to preview the PATCH payload. action=decline declines an invitation (optional comment). action=cancel cancels an event you organised and notifies attendees. action=delete permanently removes the event. Returns the updated event on update; status confirmation otherwise. Note: there is no accept action — accept invitations in the Outlook UI (Graph's accept verb is unreliable across personal/M365).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoAlias for `eventId` (canonical per the v3.7.3 alias pass).
endNoNew end time as ISO 8601 string or {dateTime, timeZone} object (action=update only)
bodyNoNew body content (action=update only)
startNoNew start time as ISO 8601 string or {dateTime, timeZone} object (action=update only)
actionYesAction to perform (required)
dryRunNoPreview the PATCH without applying it (action=update only). Returns the body that would be sent to Graph.
showAsNoFree/busy status shown to others (action=update only)
commentNoOptional comment for declining or cancelling the event
eventIdNoThe ID of the event
subjectNoNew subject (action=update only)
locationNoNew location display name (action=update only)
attendeesNoFull replacement attendee list — pass complete desired list, or [] to clear (action=update only)
categoriesNoFull replacement category list — pass [] to clear (action=update only)
importanceNoEvent importance flag (action=update only)
sensitivityNoEvent sensitivity classification (action=update only)
isOnlineMeetingNoToggle online meeting flag (action=update only)
reminderMinutesBeforeStartNoMinutes before start to fire the reminder (action=update only)
Behavior5/5

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

Thoroughly discloses destructive behavior (cancel notifies attendees, delete permanently removes), PATCH semantics (only fields passed are changed), and dryRun side-effect-free preview. This adds significant value beyond the destructiveHint annotation and covers return behavior.

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?

Despite being long, the description is well-organized by action, front-loaded with the destructive warning, and every sentence serves a purpose given the complex multi-action tool. No redundancy or filler.

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

Completeness5/5

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

Comprehensive: covers all actions, dryRun, accept limitation, return values, and PATCH merge behavior. With 17 params and no output schema, the description plus schema fully specify the tool's behavior.

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%, but the description adds critical semantics like 'only fields you pass are changed', 'full replacement list' for attendees/categories, and action-specific applicability. This enriches the schema-provided definitions.

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?

Description clearly states it manages existing calendar events (update/decline/cancel/delete) and differentiates from siblings like create-event and list-events. The four action types are enumerated, making the purpose specific and unambiguous.

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?

Provides clear guidance on when to use each action, including dryRun for previewing PATCH, and explicitly notes there is no accept action and instructs to use the Outlook UI instead. It lacks an explicit contrast with list-events/create-event but the scoping is evident.

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/littlebearapps/outlook-mcp'

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