Skip to main content
Glama

Remove a movie from a list

remove_from_list
DestructiveIdempotent

Remove a movie from a custom TMDB list by providing the list ID and movie ID.

Instructions

Remove a movie from 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>",
      "movie_id": "<movie_id>"
    },
    "name": "remove_from_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
list_idYesTMDB list ID, from get_account_lists or create_list
movie_idYesTMDB movie ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered structurally. The description adds no behavioral context beyond that — it does not say what happens if the movie is not in the list, whether the list must be owned by the user, or whether removal is reversible.

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 short sentence with no filler, and the mutating action is front-loaded. It is as compact as possible, though that compactness is part of why other dimensions are thin.

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, annotations and a fully described schema carry most of the load. However, the description omits any note on failure behavior (movie not present) or the confirmation that removal is idempotent, which would be valuable for an agent invoking a destructive call.

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%, with list_id documented as sourced from get_account_lists or create_list and movie_id as a TMDB movie ID. The description adds no parameter meaning beyond the schema, so the baseline of 3 applies.

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?

States a specific verb and resource ('Remove a movie from one of my lists') so the agent knows exactly what mutation occurs on which resource. It does not explicitly distinguish itself from add_to_list or clear_list, but the verb is unambiguous.

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 when-to-use guidance, no mention of prerequisites (e.g. the movie must already be in the list), and no reference to alternatives such as clear_list for bulk removal. Usage is only implied by the tool name and the word 'remove'.

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