Skip to main content
Glama

Update Calendar Event

update_event
Destructive

Modify an existing calendar event in Microsoft 365 by changing its subject, start and end times, location, attendees, body, reminder, or Teams meeting status.

Instructions

Update an existing calendar event

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": {
      "event_id": "<event_id>"
    },
    "name": "update_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoNew end date/time (ISO format), or the last day (YYYY-MM-DD, inclusive) when all_day is true; defaults to start then
bodyNoNew description
startNoNew start date/time (ISO format), or the first day (YYYY-MM-DD) when all_day is true
all_dayNotrue makes it an all-day event (needs start); false makes it a timed event (needs start and end). Omit to leave it as it is.
show_asNoHow the time shows in free/busy: free, tentative, busy, oof or workingElsewhere. Omit to leave it, except that changing all_day follows Outlook: free when it becomes all-day, busy when it becomes timed.
subjectNoNew subject
event_idYesThe event ID to update
locationNoNew location
reminderNofalse turns the event's reminder off; true turns it on. Omit to leave it as it is.
attendeesNoComma-separated email addresses; replaces the current attendee list when provided
time_zoneNoZone of start and end, IANA or Windows name (default: UTC). The reply shows the event's times in it too.
calendar_idNoID of the calendar the event is in, from list_calendars. Needed for a calendar shared with you by someone else; may be omitted for your own calendars.
content_typeNoBody content type: Text or HTML (default: Text)
online_meetingNoAdd a Teams meeting to the event. One-way per Graph: once enabled it cannot be turned off or re-provisioned. Default: false.
reminder_minutesNoMinutes before the start to remind, which also turns the reminder on. For an all-day event the start is midnight, so 1080 reminds at 6 pm the evening before. Graph's default is 15.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is known. The description adds nothing beyond that: it never says the update is partial (omitted fields are preserved), that attendees replaces the whole list, or that online_meeting is one-way — all of which live only in the schema, not the description.

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

Conciseness3/5

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

The single sentence is front-loaded and free of waste, but for a 15-parameter destructive mutation tool it is undersized rather than concise. Brevity here reflects under-specification, not economy of expression.

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?

The rich schema compensates for much of the missing detail, and there is no output schema requiring explanation. Still, for a destructive update with 15 parameters and non-obvious semantics (replacement vs. merge, one-way Teams meeting), a six-word description leaves the agent without any of the behavioral framing that matters most.

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 15 parameters are fully documented in the schema itself, which sets the baseline at 3. The description contributes no parameter meaning whatsoever, so it neither improves nor degrades the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Update an existing calendar event" names a clear verb and resource, so an agent knows the operation type. However, it is essentially a restatement of the title "Update Calendar Event" and adds no distinguishing scope against siblings such as create_event, delete_event, or respond_to_event.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites (event must already exist, calendar_id needed for shared calendars), and no routing to alternatives like create_event or respond_to_event. The agent must infer all selection logic from the tool name and schema alone.

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

Deploy Server

Other Tools