Skip to main content
Glama

Delete events

delete_events
DestructiveIdempotent

Removes events or periods from a timeline the user owns, by their ids.

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": {
      "timeline_id": "<timeline_id>",
      "event_ids": "<event_ids>"
    },
    "name": "delete_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idsYes
timeline_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is structured. The description adds the ownership/auth requirement and clarifies the target set (events or periods), but says nothing about irreversibility, confirmation, or what happens if some ids are invalid.

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?

One short sentence with the action and scope front-loaded and no filler. It is efficient rather than padded, though it leaves little room for the missing operational detail.

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

Completeness3/5

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

A destructive two-parameter tool with annotations covering destructiveness and idempotency, so the safety burden is largely met elsewhere. Still, partial-failure semantics and permission requirements are thin for an irreversible delete with an all-required schema and no output schema.

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%, so the description must carry the load. 'By their ids' hints that event_ids are identifiers scoped to timeline_id, but it doesn't state that both are integers, that event_ids is a list, or whether unknown/invalid ids fail the whole call.

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?

States a specific verb (Removes) and resource (events or periods) scoped to a timeline the user owns, which implicitly distinguishes it from add_events and update_event. Sibling differentiation is not explicit, but the operation is unmistakable.

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?

There is no guidance on when to use this versus update_event (e.g., clearing vs. modifying) or how to handle removing a whole period. The only usage-adjacent content is the implicit ownership prerequisite in 'a timeline the user owns'.

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