feishu-user-plugin

delete_calendar_event

Delete a calendar event, with optional notification to attendees and dissolution of linked meeting chat.

Instructions

[Official API + UAT, v1.3.7] Delete a calendar event. Requires calendar:calendar.event:write scope.

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": {
      "calendar_id": "<calendar_id>",
      "event_id": "<event_id>"
    },
    "name": "delete_calendar_event"
  }
}

Input Schema

Name	Required	Description
`calendar_id`	Yes	Calendar ID
`event_id`	Yes	Event ID
`need_notification`	No	Whether to notify attendees of the deletion (default true)
`meeting_chat_id`	No	Optional. If the event has a linked meeting chat, pass its chat_id to also dissolve it.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.10May 9, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. Adds scope but no details on permanence, notification, or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very short but includes non-essential metadata ('[Official API + UAT, v1.3.7]'). Could be cleaner.

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?

No output schema. Does not explain return values or important behavioral context like notification defaults or irreversibility.

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 coverage is 100%, so baseline is 3. Description adds no parameter information beyond what is in the schema.

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?

Clearly states the tool deletes a calendar event and specifies required scope. However, does not differentiate from siblings like 'create_calendar_event' or 'update_calendar_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?

Provides no guidance on when to use this tool vs alternatives. Only states the action and scope requirement.

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

Deploy Server