Skip to main content
Glama

Delete Calendar Event

delete_event
Destructive

Delete a Microsoft 365 calendar event by event ID, with an optional calendar ID for shared calendars. Use it to remove meetings or appointments from a user's calendar.

Instructions

Delete a 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": "delete_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYesThe event ID to delete
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/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 from structured data. The description adds nothing beyond that: it does not say whether deletion is permanent, how recurring events or attendees/cancellations are handled, or what the caller gets back. For a destructive mutation, that is a real gap.

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 description is a single short phrase with zero wasted words and is fully front-loaded. However, it is under-specified rather than well-structured; brevity here reflects missing content, not disciplined editing.

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?

This is a destructive, irreversible-looking operation with no output schema and no annotations beyond the destructive hint, so the description should carry more of the burden. It omits consequences, recurrence behavior, and any confirmation expectation, leaving an agent to infer the risk profile.

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%, and the schema itself explains that calendar_id is only needed for calendars shared by another user and where to obtain it. The description contributes no additional parameter meaning, so the baseline 3 applies.

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?

The description states a specific verb and resource ("Delete a calendar event"), which is unambiguous about what the tool does. It does not, however, differentiate this tool from sibling deletion tools or from update_event, 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 Guidelines2/5

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

There is no guidance on when to use this versus update_event (e.g., removing a single occurrence vs. the series) or other delete_* siblings. The only usage-adjacent detail, the shared-calendar case for calendar_id, lives in the schema rather than the description.

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