Skip to main content
Glama
seandkendall

productivity-mcp

by seandkendall

delete_event

Remove a calendar event using its unique ID. Specify optional account and calendar to target the correct event.

Instructions

Delete a calendar event by id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_idYes
accountNo
calendarNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for delete_event - the entry point that calls the provider's delete_event method and returns status.
    @mcp.tool()
    @_logged
    def delete_event(event_id: str, account: str | None = None, calendar: str | None = None) -> dict[str, str]:
        """Delete a calendar event by id."""
        _calendar(account).delete_event(calendar, event_id)
        return {"status": "deleted", "event_id": event_id}
  • Abstract interface definition for delete_event in CalendarProvider base class.
    @abstractmethod
    def delete_event(self, calendar: str | None, event_id: str) -> None: ...
  • Rate limit registration: 20 calls per 60-second window for delete_event.
        "delete_event": (20, 60.0),
        "bulk_set_read": (10, 60.0),
        "bulk_delete_emails": (10, 60.0),
        "bulk_move_emails": (10, 60.0),
        "create_event": (30, 60.0),
        "update_event": (30, 60.0),
    }
  • Google Calendar provider implementation - calls Google API to delete the event.
    def delete_event(self, calendar: str | None, event_id: str) -> None:
        self._svc().events().delete(
            calendarId=self._resolve_calendar(calendar), eventId=event_id
        ).execute()
  • EWS (Exchange) calendar provider implementation - deletes event via EWS API.
    def delete_event(self, calendar: str | None, event_id: str) -> None:
        acct = self._acct()
        item = acct.calendar.get(id=event_id)
        item.delete(send_meeting_cancellations="SendToAllAndSaveCopy")
  • CalDAV calendar provider implementation - finds event by UID in iCal data and deletes it.
    def delete_event(self, calendar: str | None, event_id: str) -> None:
        cal = self._find_calendar(calendar)
        for item in cal.events():
            parsed = ICal.from_ical(item.data)
            for comp in parsed.walk("VEVENT"):
                if str(comp.get("uid")) == event_id:
                    item.delete()
                    return
Behavior2/5

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

No annotations are provided, so the description must compensate. It does not disclose important traits such as irreversibility, recurrence handling, permission requirements, or side effects like cascade deletions.

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 description is a single, concise sentence with no unnecessary words. However, it could be slightly more informative without becoming verbose.

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 event deletion (recurring events, permissions, side effects) and the lack of annotation support, the description is too sparse. It does not mention return values or behavior for non-existent events, leaving important gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description only adds context for 'event_id' (by id). The optional 'account' and 'calendar' parameters are left unexplained, forcing reliance on parameter names alone.

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 verb 'delete' and the resource 'calendar event', with the identifier 'by id'. This distinguishes it from siblings like create_event, get_event, and update_event.

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 over alternatives (e.g., respond_event for cancellation) or when not to use it. No exclusions or prerequisites are mentioned.

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/seandkendall/productivity-mcp'

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