Skip to main content
Glama
Google Workspace (GWS) MCP Server

Google Workspace (GWS) MCP Server

calendar_events_delete

DestructiveIdempotent

Delete a specified Google Calendar event by calendar ID and event ID to remove unwanted or outdated entries.

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": {
      "calendarId": "<calendarId>",
      "eventId": "<eventId>"
    },
    "name": "calendar_events_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventIdYesEvent ID to delete
calendarIdYesCalendar ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered by structured data. The description adds nothing beyond that — no statement that deletion is permanent, no mention of permission/ownership requirements, and no note about what happens to recurring instances or attendees.

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?

A single front-loaded sentence with zero filler. It is efficient, though its brevity reflects under-specification rather than tight editing.

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 destructive tool with full schema coverage and rich annotations, the minimum is present. However, the description never warns that the operation is irreversible or clarifies behavior for recurring events, which is meaningful for a delete operation.

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 both required parameters (calendarId, eventId) are documented in the schema, so the baseline of 3 applies. The description contributes no additional meaning about ID formats or where those IDs come from.

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 uses a specific verb ('Delete') with a specific resource ('calendar event'), which cleanly separates it from the get/insert/list/update siblings on the same resource. It does not explicitly name any sibling or scope constraint, 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 when-to-use guidance, no prerequisites, and no mention of alternatives such as calendar_events_update for modifications. The only signal is the verb itself, which the agent must interpret unaided.

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