Skip to main content
Glama

Get collection

get_collection
Read-only

Retrieve a TMDB movie collection and all movies in that franchise by collection ID, with optional language selection.

Instructions

A movie collection (franchise) with all of its movies, e.g. the Lord of the Rings collection.

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

Input Schema

NameRequiredDescriptionDefault
languageNoResponse language as ISO 639-1 with optional ISO 3166-1 region, e.g. en-US or fr-FR. Defaults to TMDB_LANGUAGE.
collection_idYesTMDB collection ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/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 one useful behavioral fact — the response includes all movies in the collection, not just metadata — but says nothing about missing/invalid IDs, language fallback behavior, or response size.

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 front-loaded sentence with zero filler; the parenthetical '(franchise)' and the example both earn their place by disambiguating the resource. It is arguably too terse for a tool with no output schema, but nothing is redundant.

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?

With no output schema, the description carries some of the return-value burden and does note that all movies are included. However, it leaves the response structure, error conditions, and language-resolution behavior undocumented, which is thin for an agent calling this cold.

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%, so both collection_id and language are already documented with format and defaults. The Lord of the Rings example gives a concrete mental model for what a collection_id refers to, but adds no syntax or edge-case detail beyond the schema.

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 precisely — a movie collection/franchise and that it bundles all its movies — which separates it from get_movie, get_person, and get_list. It lacks an explicit verb ('retrieve'/'get'), but the resource and the concrete Lord of the Rings example make the intent 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 prerequisites, and no mention of any alternative tool. An agent must infer from the noun phrase alone that this is the lookup for franchise groupings rather than individual titles or curated lists.

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