Skip to main content
Glama

delete-specific-calendar-event

delete-specific-calendar-event
Destructive

Delete a specific calendar event from Microsoft 365. Provide calendar and event IDs; use the instance ID to remove only one occurrence instead of the entire series.

Instructions

Delete a specific calendar event.

šŸ’” TIP: Deleting a seriesMaster deletes ALL occurrences. To cancel a single occurrence, use the specific instance ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoFor destructive operations when the confirm gate is enabled (MS365_MCP_REQUIRE_CONFIRM=true; off by default). Set to true only after the user has explicitly approved this action. When the gate is on, calls without confirm: true return { error: "confirmation_required" } without touching user data.
eventIdYesValue for the 'eventId' path segment. Pass it under the name 'eventId', not as 'id'. Use the 'id' field of the event object as returned by Microsoft Graph.
If-MatchNoETag
calendarIdYesValue for the 'calendarId' path segment. Pass it under the name 'calendarId', not as 'id'. Use the 'id' field of the calendar object as returned by Microsoft Graph.
includeHeadersNoInclude response headers (including ETag) in the response metadata
excludeResponseNoExclude the full response body and only return success or failure indication
Behavior5/5

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

Annotations declare destructiveHint=true, but the description adds a specific behavioral disclosure: deleting a seriesMaster cascades to all occurrences. This is valuable operational context beyond the annotation and helps the agent anticipate side effects.

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?

The description is a single declarative sentence plus a succinct tip. Every word earns its place, and the most critical behavioral caveat is placed prominently after the main purpose. No filler or redundancy.

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 a destructive operation, the description covers the main side effect (seriesMaster cascade) and points to the correct ID type. It lacks explicit guidance on when to use this vs. siblings, but the schema covers parameter detail and the annotations cover destructive intent. The tool is simple enough that the provided context is largely sufficient.

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 description coverage is 100%, so parameters are already documented. The description adds meaning by relating the eventId parameter to seriesMaster versus instance semantics, which is not fully captured in the schema's standard 'id' description. This enhances understanding of how to fill eventId correctly.

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 states 'Delete a specific calendar event' with a clear verb and resource, and the name includes 'specific' to distinguish from general delete operations. The tip about seriesMaster further clarifies scope (deletes all occurrences when a series master is targeted), which aids selection among the many calendar siblings.

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?

The description provides a useful tip about seriesMaster versus instance deletion, implicitly indicating when to use a specific instance ID. However, it does not explicitly state when to choose this tool over alternatives like delete-calendar-event or cancel-calendar-event, nor does it mention any exclusions or prerequisites.

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/A-Impact-Pavel/ms365-mcp'

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