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}`,
          },
        ],
      };
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Delete' implies a destructive mutation, the description doesn't specify whether this requires special permissions, if deletions are permanent or reversible, what happens to associated data (e.g., attendees), or any rate limits. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 that front-loads the core action ('Delete a calendar event') without unnecessary words. Every part of the sentence earns its place by specifying the resource and key parameter. There is zero waste or redundancy.

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?

Given the complexity of a destructive operation with no annotations and no output schema, the description is incomplete. It lacks critical context such as error handling, confirmation requirements, return values, or side effects. For a tool that permanently modifies data, this minimal description leaves too many unknowns for safe and effective use.

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 ('eventId' as required, 'calendar' as optional). The description mentions 'by its ID' which aligns with the 'eventId' parameter but adds no additional semantic context beyond what the schema provides. With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but doesn't detract either.

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 clearly states the action ('Delete') and resource ('calendar event by its ID'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'update_event' or 'list_events', but the verb 'Delete' is specific enough to distinguish it as a destructive operation. This is not a tautology since it provides more information than just the tool name.

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 doesn't mention prerequisites (e.g., needing an event ID from 'list_events' or 'get_calendars'), when not to use it (e.g., for read-only operations), or explicit alternatives among siblings like 'update_event'. The agent must infer usage from the tool name alone.

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/cqyefeng119/windows-outlook-mcp'

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