Skip to main content
Glama

Create a list

create_list

Creates a new custom movie list on your TMDB account and returns its list_id, so you can add movies to that list later.

Instructions

Create a new custom list on my account. Returns the new list_id. TMDB v3 lists hold movies only.

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": {
      "name": "<name>"
    },
    "name": "create_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesList name
languageNoISO 639-1 language of the list, e.g. en
descriptionNoList description

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds real value beyond them: it discloses the return value (new list_id) and a substantive domain constraint that TMDB v3 lists hold movies only, which affects how an agent should organize content. It omits any mention of authentication/session requirements implied by 'my account'.

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?

Three short sentences: action, return value, then the key constraint. It is front-loaded with the operation and wastes no words.

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 three-parameter mutation with no output schema, the description covers the action, the returned identifier, and the content-type limitation. Annotations carry the risk profile. Only the authentication/session requirement for 'my account' is left implicit.

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 name, language pattern and description maxLength all documented in the schema itself. The description adds no format, default, or constraint detail beyond that, so the baseline 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 ('Create a new custom list') plus the owning scope ('on my account'), and the word 'custom' implicitly separates it from favorite/watchlist siblings. It does not name a specific sibling tool to differentiate against, but the operation is unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'custom list on my account' suggests this is for creating a container rather than adding items (add_to_list) or fetching one (get_list). The 'movies only' note hints that TV list operations belong elsewhere, but no explicit when-to-use or when-not-to-use statement is given.

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