Skip to main content
Glama
the-events-calendar

The Events Calendar MCP Server

Official

tec-calendar-delete-entities

Delete or trash calendar posts such as events, venues, organizers, or tickets. Choose between recoverable trash or permanent deletion.

Instructions

Delete or trash a calendar post (Event, Venue, Organizer, or Ticket).

  • Default (force=false or omitted): Moves posts to trash where they can be restored

  • Permanent delete (force=true): Permanently deletes posts with no option to restore

Delete Behaviors

  • Default (force=false): Moves to trash (recoverable)

  • Force delete (force=true): Permanent deletion (not recoverable)

Best Practices

  • Always use default trash unless permanent deletion is required

  • Consider checking post details before deletion

  • For events, verify dates and timezone context first

Examples

Event Deletion

The Events Calendar event post type with date, location, and ticketing information

Move to trash (default, recoverable)

{
  "postType": "event",
  "id": 123
}

Permanent deletion (not recoverable)

{
  "postType": "event",
  "id": 124,
  "force": true
}

Venue Deletion

Location where events take place, including address and contact information

Move to trash (default, recoverable)

{
  "postType": "venue",
  "id": 456
}

Permanent deletion (not recoverable)

{
  "postType": "venue",
  "id": 457,
  "force": true
}

Organizer Deletion

Person or organization responsible for hosting events

Move to trash (default, recoverable)

{
  "postType": "organizer",
  "id": 789
}

Permanent deletion (not recoverable)

{
  "postType": "organizer",
  "id": 790,
  "force": true
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
postTypeYesThe type of post to delete
idYesPost ID to delete
forceNotrue for permanent delete, false for trash (default: false)
Behavior4/5

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

No annotations provided, so description carries full burden. It explains default recoverable trash vs permanent deletion. Does not mention potential side effects like cascading deletes or access requirements, but is transparent about the core behavior.

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?

Well-structured with headings, bullet points, and examples. Front-loaded with purpose. Some redundancy (Delete Behaviors section repeats prior info), but overall efficient and readable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers behavior for all post types with examples and best practices. Missing details on cascading effects or output format, but given no output schema and simplicity of tool, it is sufficiently complete for an agent.

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

Parameters4/5

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

Schema coverage is 100%, but description adds value by explaining the force parameter's effect and providing examples for each post type. The examples clarify usage beyond schema definitions.

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?

Description clearly states the verb (delete or trash) and the resources (Event, Venue, Organizer, Ticket). It distinguishes between default trash and permanent delete, and the name differentiates it from create-update and read siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides best practices (use default trash unless permanent deletion required) and suggests checking post details before deletion. However, it does not explicitly contrast with alternatives or provide when-not-to-use scenarios.

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/the-events-calendar/mcp-server'

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