Skip to main content
Glama

Get list

get_list
Read-only

Fetches a TMDB list's items with pagination and language options; include a movie ID to verify whether that movie is on the list.

Instructions

A TMDB list with its items. Pass movie_id to also check whether that movie is on the list.

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": "get_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResults page, 1-500. Each page holds up to 20 results.
list_idYesTMDB list ID, from get_account_lists or create_list
languageNoResponse language as ISO 639-1 with optional ISO 3166-1 region, e.g. en-US or fr-FR. Defaults to TMDB_LANGUAGE.
movie_idNoTMDB movie ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful context about the response shape (a list plus its items) and the dual role of movie_id, but says nothing about private lists, access requirements, or pagination limits.

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?

Two compact sentences with no filler, and the core resource description is front-loaded. The first sentence is a noun fragment rather than a complete statement of action, a minor structural weakness.

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?

This is a simple read tool with a fully described four-parameter schema and no output schema, and the description conveys what comes back and how movie_id changes the result. Only edge-case behavior such as private or missing lists is left unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so page, list_id, and language are already well documented. The description nonetheless adds genuine meaning for movie_id, explaining that supplying it triggers a membership check rather than just naming a movie — a semantic the schema's bare "TMDB movie ID" does not convey.

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?

The description identifies the resource and its payload ("A TMDB list with its items") and flags a distinctive secondary behavior for movie_id. The verb is only implied by the tool name rather than stated, and it does not distinguish this from siblings like get_movie_list or get_account_lists.

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?

The only conditional guidance is "Pass movie_id to also check whether that movie is on the list," which tells the agent when to use that parameter but not when to choose this tool over get_account_lists or get_movie_list. Usage is implied rather than stated.

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