Skip to main content
Glama

delete_event

Remove calendar events from Outlook by specifying the event ID. This tool helps manage your schedule by deleting unwanted or outdated appointments directly through the Outlook MCP Server.

Instructions

Delete a calendar event by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventIdYesEvent ID to delete
calendarNoCalendar name (optional)

Implementation Reference

  • Core handler function that executes PowerShell script to delete the Outlook calendar event using the provided eventId via Outlook COM interop.
    async deleteEvent(options: {
      eventId: string;
      calendar?: string;
    }): Promise<{ success: boolean; message: string }> {
      try {
        const script = `
          try {
            Add-Type -AssemblyName "Microsoft.Office.Interop.Outlook" -ErrorAction Stop
            $outlook = New-Object -ComObject Outlook.Application -ErrorAction Stop
            $namespace = $outlook.GetNamespace("MAPI")
            
            # Get appointment
            $appointment = $namespace.GetItemFromID("${options.eventId.replace(/"/g, '""')}")
            
            if (-not $appointment) {
              throw "Event not found with ID: ${options.eventId.replace(/"/g, '""')}"
            }
            
            # Delete the appointment
            $appointment.Delete()
            
            Write-Output ([PSCustomObject]@{
              Success = $true
            } | ConvertTo-Json -Compress)
            
          } catch {
            Write-Output ([PSCustomObject]@{
              Success = $false
              Error = $_.Exception.Message
            } | ConvertTo-Json -Compress)
          }
        `;
    
        const result = await this.executePowerShell(script);
        const cleanResult = result.replace(/[\u0000-\u0008\u000B\u000C\u000E-\u001F\u007F]/g, '').trim();
        const data = JSON.parse(cleanResult);
    
        if (!data.Success) {
          throw new Error(data.Error || 'Failed to delete event');
        }
    
        return {
          success: true,
          message: 'Event deleted successfully'
        };
      } catch (error) {
        throw new Error(`Failed to delete event: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
  • src/index.ts:378-395 (registration)
    Tool registration in the MCP server's tools array, including name, description, and input schema for delete_event.
    {
      name: "delete_event",
      description: "Delete a calendar event by its ID",
      inputSchema: {
        type: "object",
        properties: {
          eventId: {
            type: "string",
            description: "Event ID to delete"
          },
          calendar: {
            type: "string",
            description: "Calendar name (optional)"
          }
        },
        required: ["eventId"]
      }
    },
  • Input schema definition specifying eventId as required string and optional calendar string.
    inputSchema: {
      type: "object",
      properties: {
        eventId: {
          type: "string",
          description: "Event ID to delete"
        },
        calendar: {
          type: "string",
          description: "Calendar name (optional)"
        }
      },
      required: ["eventId"]
    }
  • MCP request handler case that extracts arguments, calls the core deleteEvent handler, and formats the response.
    case 'delete_event': {
      const result = await outlookManager.deleteEvent({
        eventId: (args as any)?.eventId,
        calendar: (args as any)?.calendar
      });
      return {
        content: [
          {
            type: 'text',
            text: `${result.success ? '✅' : '❌'} **Event Deletion**\n\n${result.message}`,
          },
        ],
      };
    }

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but lacks behavioral details. It states the action ('Delete') but does not disclose critical traits like required permissions, whether deletion is permanent or reversible, error handling (e.g., for invalid IDs), or side effects (e.g., notifications to attendees).

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, efficient sentence with zero waste. It is front-loaded with the core action and resource, making it easy to parse quickly without unnecessary elaboration.

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?

For a destructive tool with no annotations and no output schema, the description is incomplete. It lacks context on permissions, consequences, error cases, or return values, leaving significant gaps for safe and effective use by an AI agent.

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%, so the schema already documents both parameters ('calendar' as optional name, 'eventId' as required ID). The description adds no additional meaning beyond implying 'eventId' is used for deletion, aligning with but not enriching the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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 clearly states the specific action ('Delete') and resource ('a calendar event'), with precise targeting ('by its ID'). It distinguishes from siblings like 'create_event', 'update_event', and 'list_events' by focusing on removal rather than creation, modification, or listing.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., needing an existing event ID), exclusions (e.g., not for recurring events), or comparisons to siblings like 'update_event' for modifications instead of deletion.

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