Skip to main content
Glama

Delete a logged event

delete_event
DestructiveIdempotent

Delete a logged finish/re-watch/re-read event on one item. The undo for log_event. With no event_date, event_id, or all, and more than one event on the item, nothing is deleted and the events are listed with 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": {
      "media_type": "<media_type>"
    },
    "name": "delete_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNoDelete every logged event on the item.
titleNoExact title of the item (or pass item_id)
item_idNoLibrary item id (UUID), as shown by get_details. Preferred over title.
event_idNoDelete exactly this event, by the id delete_event reported.
event_dateNoDelete the event on this date: YYYY-MM-DD, or YYYY-MM / YYYY to cover a whole period. When more than one event matches, nothing is deleted and they are listed with ids; pass event_id, or all: true alongside event_date to delete every match.
media_typeYesType of media

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / media_type / enum
      Previous value: -[
      -  "book",
      -  "movie",
      -  "album",
      -  "show",
      -  "anime",
      -  "podcast",
      -  "game",
      -  "manga",
      -  "comic"
      -]New value: +[
      +  "book",
      +  "movie",
      +  "album",
      +  "show",
      +  "anime",
      +  "podcast",
      +  "game",
      +  "manga",
      +  "comic",
      +  "boardgame"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / media_type / enum
      Previous value: -[
      -  "book",
      -  "movie",
      -  "album",
      -  "show",
      -  "anime",
      -  "podcast",
      -  "game",
      -  "manga"
      -]New value: +[
      +  "book",
      +  "movie",
      +  "album",
      +  "show",
      +  "anime",
      +  "podcast",
      +  "game",
      +  "manga",
      +  "comic"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / event_date / description
      Previous value: -"Delete the event(s) on this date: YYYY-MM-DD, or YYYY-MM / YYYY to cover a whole period."New value: +"Delete the event on this date: YYYY-MM-DD, or YYYY-MM / YYYY to cover a whole period. When more than one event matches, nothing is deleted and they are listed with ids; pass event_id, or all: true alongside event_date to delete every match."
  4. Added

TDQS

A4.1/5.0
Behavior4/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 covered. The description adds genuinely non-obvious behavior beyond that: with no selector and multiple events, nothing is deleted and events are returned with ids, which is a critical safety-by-no-op trait an agent must know to handle the response.

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?

Three short sentences, front-loaded with purpose and the sibling relationship, with no filler. The third sentence largely duplicates what the event_date schema already says, which is the only redundancy.

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?

For a six-parameter destructive tool with no output schema, the description covers the essential ambiguity path and tells the agent what comes back (events listed with ids) when nothing is deleted. It does not discuss partial failures, but all parameters are fully documented in the schema.

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 description coverage is 100% and the event_date parameter already explains the multi-match listing behavior and the event_id / all:true workaround in detail. The description restates the same selector interaction rather than adding new meaning, so the baseline 3 applies.

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?

"Delete a logged finish/re-watch/re-read event on one item" gives a specific verb plus a precisely scoped resource, and "The undo for log_event" ties it to the sibling it inverts. An agent can distinguish this from delete_item or delete_review without inspecting any schema.

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?

The inverse relationship to log_event establishes clear when-to-use context, and the no-selector case is spelled out with its exact outcome. It stops short of naming an explicit exclusion (e.g. use delete_item to remove the item itself), so it is clear context without full routing guidance.

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