Skip to main content
Glama

Add a movie to a list

add_to_list

Add a movie to a specified TMDB list using its list ID and movie ID, so users can organize titles into custom collections.

Instructions

Add a movie to 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": "add_to_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.7/5.0
Behavior2/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, open-world mutation, so the description needs to add context such as duplicate handling (relevant given idempotentHint=false), whether the movie must exist in TMDB, or auth requirements. It adds none of that, leaving behavioral disclosure entirely to structured fields.

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 wasted words and the action front-loaded. Its brevity is appropriate, though the terseness borders on under-specification rather than true efficiency.

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?

This is a simple two-parameter mutation with a fully documented schema and complete annotations, so not much is strictly required. Still, for a write operation that can append duplicates, the description omits any confirmation of scope or side effects, leaving it only minimally adequate.

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 explicitly sourced from get_account_lists or create_list and movie_id identified as a TMDB movie ID, so the schema does the heavy lifting. The description adds no further meaning about parameter formats or constraints; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a concrete verb and resource (add a movie to a list), which is better than a bare restatement of the name, but it is nearly identical to the title and gives no differentiation from siblings such as remove_from_list or create_list. An agent cannot tell from the text alone what makes this the right add-path.

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 prerequisites (e.g., list must already exist, obtained via create_list or get_account_lists), and no pointer to alternatives such as remove_from_list for the inverse operation. The schema hints where list_id comes from, but the description itself offers nothing.

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