Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tmdb_collection

Fetch a TMDB movie franchise collection by ID or slug, returning its title, overview, source links, and member movies with release and poster details.

Instructions

Get a TMDB collection. Returns a TMDB collection (a movie franchise grouping) by id, which can be the collection id or an id-slug. The response has the collection title, overview, uri and source_url, plus its member movies, each with id, title, overview, poster URL, release date and uri.

Input Schema

NameRequiredDescriptionDefault
idYesTMDB collection id or id-slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. 'Get' implies read-only and the response fields are enumerated, but it does not explicitly state read-only/no side effects, nor mention auth, rate limits, or error behavior for an invalid id.

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?

Three sentences, front-loaded with purpose then input then output. There is slight redundancy in 'Get a TMDB collection. Returns a TMDB collection...' but the structure is otherwise efficient and easy to scan.

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?

No output schema exists, so the description must describe returns; it does so thoroughly by listing the collection-level fields and each member movie's fields. It omits error cases and other non-happy-path behavior, but for a simple read-by-id tool this is largely complete.

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% and the schema already documents the sole `id` parameter as 'TMDB collection id or id-slug.' The description repeats that meaning without adding syntax or format details beyond the schema, 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 (Get) and resource (TMDB collection), and clarifies the concept as 'a movie franchise grouping,' which inherently separates it from tmdb_movie and tmdb_tv. It does not explicitly name or contrast with a sibling tool, so it is clear but under-differentiated at the 4 level.

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?

The description offers no when-to-use guidance, no conditions for selecting this tool, and no alternatives such as tmdb_search or tmdb_movie. The only usage signal is the implicit requirement of an id.

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

Deploy Server

Other Tools