Skip to main content
Glama

Delete one of my events (it goes to Trash and can be restored)

connections_event_delete
Destructive

Use this when the member asks to delete, remove, get rid of or clean up one of their own hosted events by id ('delete my test events', 'remove that draft'). The event goes to the member's Trash with every date of its series and its guest list, and connections_event_restore brings it back exactly as it was, by the same id, for as long as the member's plan keeps deletions restorable (connections_storage_list_trash shows each item's last day). Only the event's owner can delete it; a co-host cannot. An event that still holds paid tickets is not deleted until it is canceled (connections_event_cancel refunds them). A published event's page stops working at once and the guests are not messaged, so for a real event people were coming to, cancel it instead, which tells visitors it was canceled. ALWAYS call it with dry_run:true first: it names the event and how many guests it has, and you confirm with the member before calling it again for real. To delete several, call it once per event.

Input Schema

NameRequiredDescriptionDefault
personNoLinked person to run this call as (first name). Omit to run as the connection's holder.
dry_runNotrue = name the event and its guests, and delete nothing. Always do this first and confirm with the member.
projectNoWorkspace to run this call in (id or name).
event_idYesThe id of the member's own event (find it with connections_events_list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description explains that the event goes to Trash with its series dates and guest list, remains restorable by the same id while the plan allows, and only the owner can delete it. It also discloses that a published event's page stops working immediately and guests are not messaged, which is critical behavioral context for a destructive operation.

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 front-loaded with the trigger and scope, then layers in restoration, ownership, ticket, cancellation, and dry-run details. It is appropriately dense for a destructive tool, though the dry_run instruction partially repeats the schema description.

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

Completeness5/5

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

With no output schema and only general annotations, the description fully carries the burden: it covers restoration, ownership restrictions, ticket constraints, guest notification behavior, page status effects, dry-run workflow, and multi-delete handling.

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%, so the baseline is 3. The description adds meaningful workflow semantics for dry_run (it names the event and guest count without deleting) and clarifies event_id as the member's own event, though it does not discuss person or project.

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 states a specific verb and resource: delete one of the member's own hosted events by id. It explicitly distinguishes this from related siblings such as connections_event_restore and connections_event_cancel, so an agent can identify the tool's exact scope.

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

Usage Guidelines5/5

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

It gives concrete trigger phrases ('delete my test events', 'remove that draft') and clear exclusions: use cancel instead for real events people were coming to, and events with paid tickets must be canceled first. It also instructs calling dry_run:true first and confirms one-event-per-call behavior.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources