Skip to main content
Glama

graph_update_event

Modify an existing Outlook calendar event by ID, updating only the fields you provide—such as time, subject, attendees, location, body, reminders, or categories.

Instructions

Update an existing calendar event. Only provided fields are updated.

Args: event_id: The event ID to update. subject: New subject/title. start_datetime: New start time (ISO 8601). Requires timezone. end_datetime: New end time (ISO 8601). Requires timezone. timezone: Timezone for start/end times. body: New body/description. location: New location name. attendees: New list of required attendee email addresses. is_html: Whether the body is HTML (default: plain text). is_all_day: Whether the event lasts all day (default false). Graph expects midnight start and end times for all-day events. show_as: Free/busy status: "free", "tentative", "busy", "oof", "workingElsewhere", or "unknown" (default "busy"). sensitivity: Sensitivity: "normal", "personal", "private", or "confidential" (default "normal"). reminder_minutes_before_start: Reminder lead time in minutes. Negative leaves the reminder unchanged (default -1). optional_attendees: New list of optional attendee email addresses, merged with attendees. categories: Outlook category names to tag the event with. allow_new_time_proposals: Whether attendees may propose new times (default true). response_requested: Whether attendees are asked to respond (default true). user: Shared or delegated calendar owner address or user ID to act on. Empty targets your own calendar. Requires the delegated Calendars.Read.Shared or Calendars.ReadWrite.Shared permissions.

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": "graph_update_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
userNo
is_htmlNo
show_asNobusy
subjectNo
event_idYes
locationNo
timezoneNo
attendeesNo
categoriesNo
is_all_dayNo
sensitivityNonormal
end_datetimeNo
start_datetimeNo
optional_attendeesNo
response_requestedNo
allow_new_time_proposalsNo
reminder_minutes_before_startNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses partial-update semantics, that start/end times require a timezone, that all-day events expect midnight boundaries, that reminder_minutes_before_start=-1 leaves the reminder untouched, that optional_attendees are merged with attendees, and that shared calendars need Calendars.ReadWrite.Shared. It does not say whether attendees are re-invited/notified, whether categories replace or append, or what a failed update returns.

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 operative rule is front-loaded in the first two sentences, and the Args block is scannable with one line per parameter. The docstring-style enumeration is long, but with 18 parameters nearly every line carries non-obvious information, so little is wasted.

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?

For an 18-parameter mutation tool with no annotations and no output schema, the description covers the mutation semantics, defaults, and permission requirements well. The remaining gap is the response side: nothing indicates what a successful update returns or how partial failures are reported, which matters given there is no output schema to fall back on.

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

Parameters5/5

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

Schema description coverage is 0% across 18 parameters, and the description compensates by documenting every one of them with meaning beyond the schema: ISO 8601 format and timezone dependency for the datetimes, the full enum vocabularies for show_as and sensitivity, the -1 sentinel for reminders, the merge behavior of optional_attendees, and the empty-string default for `user`. This is exactly the compensation a low-coverage schema requires.

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

Purpose4/5

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

States a specific verb and resource ("Update an existing calendar event") plus the key partial-update rule ("Only provided fields are updated"), which separates it from graph_create_event and graph_delete_event by implication. It never names a sibling or explicitly rules out alternatives, so it stops short of a 5.

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?

Usage is implied by the verb and by the partial-update note, and the `user` parameter documents the shared/delegated-calendar case with its required permissions. There is no explicit when-to-use/when-not guidance, no mention of how this differs from graph_cancel_event or graph_respond_to_event, and no stated prerequisites such as needing an existing event_id.

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