Skip to main content
Glama

Clear a list

clear_list
DestructiveIdempotent

Remove all items from a TMDB list while keeping the list itself intact.

Instructions

Remove every item from one of my lists. The list itself is kept.

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": "clear_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

A4/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 carried for the agent. The description adds genuine value by stating the blast radius (all items destroyed, list object preserved). It omits irreversibility/confirmation expectations, so it adds context but not rich behavior.

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, zero filler, with the destructive scope front-loaded and the preservation guarantee directly after it. Every clause earns its place.

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-parameter destructive operation with full annotation coverage and full schema documentation, the description supplies what is missing: the scope of destruction and what remains. No output schema exists, but a void-style empty operation needs no return-value explanation.

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?

A single parameter with 100% schema description coverage that already documents list_id as a TMDB list ID sourced from get_account_lists or create_list. The description adds no meaning beyond the schema, 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?

States a specific verb and resource ("Remove every item from one of my lists") and immediately disambiguates from sibling delete_list by noting "The list itself is kept." An agent can distinguish emptying from deleting without consulting 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 second sentence implicitly routes the agent away from delete_list by clarifying the list survives the operation, giving a clear condition for choosing this tool. It stops short of naming the alternative explicitly or stating when not to use it (e.g., partial removal via remove_from_list).

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