Skip to main content
Glama

Remove from a list

remove_from_list
DestructiveIdempotent

Remove an item from a list by title, or exactly by media_type + item_id. The item stays in the library.

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": {
      "list_name": "<list_name>"
    },
    "name": "remove_from_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoThe item title (exact title preferred; partial match supported)
item_idNoLibrary item id (UUID), as shown by get_details. When given, title is ignored.
list_nameYesThe list to remove from
media_typeNoOptional: only match entries of this type

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. Added

TDQS

A3.8/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 genuine context beyond them by scoping the destruction: only the list entry is removed and "the item stays in the library," which prevents an agent from assuming a library-level delete. It still omits failure behavior for non-members or ambiguous partial titles.

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

Conciseness5/5

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

Two short sentences, both load-bearing: the first states the operation and its matching modes, the second states the blast radius. Nothing is redundant or buried.

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 single-required-param tool with full schema coverage, rich annotations, and no output schema, this covers the essentials: how to target the entry and what is and is not destroyed. The remaining gap is how ambiguous title matches resolve and what an unsuccessful removal returns.

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 the baseline is 3. The description adds only the precedence rule (title lookup versus exact media_type + item_id lookup), and the word "exactly" hints that item_id matching is precise while title matching is looser — a small but real addition over the schema's own wording.

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?

The description gives a concrete verb and resource ("Remove an item from a list") plus the two supported lookup modes (title or media_type + item_id). The clause "The item stays in the library" distinguishes it from deletion-style siblings such as delete_item, though it never names an alternative tool to route to.

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

Usage Guidelines3/5

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

Usage is implied by the two matching modes and by the clarifying note that the library item survives, which tells the agent this is a list-membership change rather than a deletion. However, it never states when to prefer remove over remove_from_shelf, nor what happens if the item is not on the list, leaving the agent to infer the boundary.

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