Skip to main content
Glama

manage-event

Destructive

Update event details like subject, time, attendees, or location; decline invitations; cancel or delete events. Preview changes with dry-run before applying.

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

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

The description details the PATCH behavior for updates (only passed fields changed), outlines the effects of cancel (notifies attendees) and delete (permanent removal), and explains dryRun preview. Annotations already indicate destructiveness, but the description adds valuable context beyond that.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with action-based sections, but it is somewhat long. It effectively front-loads the key intent and destructive nature.

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?

Given 17 parameters and no output schema, the description fully explains return values and behavior for each action, including limitations like missing accept action. It is complete for the tool's complexity.

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?

With 100% schema coverage, the description adds context by grouping parameters per action and explaining full replacement semantics for attendees and categories, but the schema itself is already descriptive.

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 that the tool manages existing calendar events with four specific actions (update, decline, cancel, delete). It distinguishes itself from sibling tools like 'create-event' and 'list-events' by focusing on modification and destruction.

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

Usage Guidelines5/5

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

The description provides explicit guidance for each action, including when to use dryRun, and explicitly states that there is no 'accept' action, directing users to the Outlook UI instead.

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