Skip to main content
Glama

delete_event

Remove a calendar event from Google Calendar using the event ID. Ideal for managing or canceling scheduled events directly through the Google Toolbox.

Instructions

Delete a calendar event

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_idYes

Implementation Reference

  • The @mcp.tool decorator registers and defines the 'delete_event' tool handler. It authenticates with Google, builds the Calendar service, deletes the event by ID from the primary calendar, logs the action, and returns success or detailed error messages.
    @mcp.tool(
        name="delete_event",
        description="Delete a calendar event",
    )
    async def delete_event(event_id: str) -> str:
        """
        Delete a calendar event
        
        Args:
            event_id (str): Event ID to delete
            
        Returns:
            str: Success message
        """
        creds = get_google_credentials()
        if not creds:
            return "Google authentication failed."
    
        try:
            service = build('calendar', 'v3', credentials=creds)
            service.events().delete(calendarId='primary', eventId=event_id).execute()
            logger.info(f"이벤트 삭제됨: {event_id}")
            return f"이벤트 삭제 성공. 이벤트 ID: {event_id}"
    
        except HttpError as error:
            logger.error(f"API 오류 발생: {error}")
            if error.resp.status == 404:
                return f"ID '{event_id}'의 이벤트를 찾을 수 없습니다."
            return f"Calendar API 오류: {error.resp.status} - {error.content.decode()}"
        except Exception as e:
            logger.exception("이벤트 삭제 중 오류:")
            return f"예상치 못한 오류 발생: {str(e)}"
  • server.py:201-206 (registration)
    The get_available_google_tools resource lists 'delete_event' among available tools, indicating its registration in the server.
        "list_emails", "search_emails", "send_email", "modify_email",
        "list_events", "create_event", "update_event", "delete_event",
        "search_google", "read_gdrive_file", "search_gdrive"
    ]
    logger.info(f"Resource 'get_available_google_tools' 호출됨. 반환: {available_google_tools}")
    return available_google_tools
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Delete' which implies a destructive mutation, but doesn't specify whether this is reversible, what permissions are required, or what happens to associated data (e.g., notifications, attendees). For a destructive tool with zero annotation coverage, this leaves significant behavioral gaps.

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, clear sentence with zero wasted words. It's appropriately sized for a simple tool and front-loads the essential information 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?

Given that this is a destructive mutation tool with no annotations, no output schema, and minimal parameter documentation, the description is incomplete. It doesn't address critical aspects like error conditions, confirmation requirements, or what happens post-deletion, which are essential for safe tool invocation.

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?

The schema description coverage is 0%, so the description must compensate for undocumented parameters. It mentions 'a calendar event' which implies the 'event_id' parameter, but doesn't explain what format the ID should be, where to obtain it, or any validation rules. This adds minimal semantic value beyond what's inferred from the parameter name.

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 the resource ('a calendar event'), which provides a specific verb+resource combination. However, it doesn't differentiate this tool from its sibling 'update_event' in terms of destructive vs. non-destructive operations, which would be helpful for sibling differentiation.

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 like 'update_event' or 'create_event'. There's no mention of prerequisites (e.g., needing an event_id), exclusions, or contextual factors that would help an agent decide between this and other event-related tools.

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

Related 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/jikime/py-mcp-google-toolbox'

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