Skip to main content
Glama

delete_list

Delete a custom Infinite Backlog list by providing its list ID and setting confirm to true. Use it to remove lists you no longer need.

Instructions

Delete one of your custom lists. Needs confirm=true.

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_id": "<list_id>"
    },
    "name": "delete_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
list_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that confirmation is required, but does not state whether deletion is permanent, what happens to list contents, or what permissions are needed.

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 front-load the core action and the confirmation constraint with no wasted wording.

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?

For a simple two-parameter destructive tool with an output schema, it meets the minimum by stating the action and confirmation requirement. However, with no annotations, it should say more about irreversibility and side effects before an agent commits to deletion.

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 0%, so the description must add meaning. It clarifies that confirm must be true, which is not conveyed by the boolean schema alone, and "one of your custom lists" loosely indicates what list_id refers to, but no further detail is given.

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 uses a specific verb and resource: "Delete one of your custom lists." It clearly identifies the operation and target, distinguishing it from sibling tools like delete_custom_tag, delete_game_copy, and delete_game_review by resource type.

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?

It offers only a parameter requirement ("Needs confirm=true") and no guidance on when to use this tool versus alternatives such as update_list or get_list. There is no mention of prerequisites, consequences, or exclusions.

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