Skip to main content
Glama

graph_delete_event

Deletes a calendar event by event ID, optionally targeting a shared or delegated calendar by providing the owner’s address or user ID.

Instructions

Delete a calendar event.

Args: event_id: The event ID to delete. 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_delete_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
userNo
event_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does usefully disclose that acting on a shared/delegated calendar requires Calendars.Read.Shared or Calendars.ReadWrite.Shared permissions. It does not state that deletion is irreversible, whether attendees are notified, or how recurring series/instances are handled, which are exactly the behavioral facts an agent needs before a destructive call.

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 one-line purpose is front-loaded and the Args block is compact. The docstring-style formatting is boilerplate but each line carries parameter information, so little is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter deletion with no output schema, the definition covers the parameters and shared-calendar permissions adequately. It stops short of the destructive-operation context (reversibility, notification side effects, recurring-event scope) that matters most here given the absence of annotations.

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 coverage is 0%, so the description must document both parameters, and it does: event_id is identified as the target event, and user is explained with its default meaning (empty targets your own calendar) plus the permission implications. The event_id note is close to tautological, but the user parameter gains genuine semantics not present in the bare schema.

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 opens with a specific verb and resource ("Delete a calendar event"), so the operation is unambiguous. It does not, however, distinguish itself from close siblings like graph_cancel_event or graph_update_event, so an agent must infer the delete-vs-cancel distinction on its own.

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 explicit guidance on when to delete versus cancel an event, nor on prerequisites beyond the delegated-permission note for shared calendars. The agent is left to infer that graph_cancel_event is the alternative when attendees should be notified.

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