Skip to main content
Glama

Delete a list

delete_list
DestructiveIdempotent

Permanently remove a TMDB custom list by ID, including lists created with create_list or found via get_account_lists. Use it to clean up lists you no longer need.

Instructions

Permanently delete one of my lists.

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
list_idYesTMDB list ID, from get_account_lists or create_list

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/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 covered by structured data. The description contributes "permanently," reinforcing that the deletion is not reversible, but says nothing about what happens to the list's items or whether any preconditions (ownership, non-empty list) apply.

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?

A single front-loaded sentence with no wasted words, and the critical qualifier "permanently" appears immediately after the verb. Its brevity skirts under-specification rather than achieving true economy, which keeps it from a 5.

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 destructive, one-parameter tool with full annotation coverage and no output schema, the annotations carry most of the behavioral weight, so the description is minimally adequate. It still leaves open the consequences for contained items and any preconditions, which matter for an irreversible operation.

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 single list_id parameter is documented with its source (get_account_lists or create_list). The description adds no meaning beyond that, so the baseline of 3 applies when the schema does the heavy lifting.

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?

"Permanently delete one of my lists" names a specific verb (delete) and resource (list), and the adverb "permanently" distinguishes it from reversible operations like clear_list or remove_from_list. It does not explicitly name those siblings, so an agent must infer the distinction from the adverb alone.

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 explicit guidance on when to use this versus clear_list (which empties a list) or remove_from_list (which pulls items). The word "permanently" implies irreversibility but the description never states a condition for selecting this tool over its siblings.

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