Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

imdb_title_trivia

Get IMDb trivia for a title by providing its IMDb ID or URL. Returns facts with spoiler flags and categories.

Instructions

IMDb title trivia. Returns the trivia IMDb lists for a title. Pass exactly one of id or url. Each entry in facts has the text, a spoiler flag and, for grouped items, a category such as Director Trademark. total is the count IMDb lists and has_more is true when only part is returned.

Input Schema

NameRequiredDescriptionDefault
idNoIMDb title id
urlNoAbsolute https://www.imdb.com/title/<id>/ URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the full burden and does so well: it discloses the shape of `facts` entries (text, spoiler flag, category), plus `total` and `has_more` pagination semantics. It stops short of stating read-only/auth/rate-limit behavior, keeping it just under the top mark.

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 tight sentences, front-loaded with purpose, then the invocation constraint, then return structure. No sentence is wasted and each adds distinct value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description explains the return fields and pagination behavior, so an agent knows both how to call it and what to expect back. Nothing essential for correct invocation is missing.

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% and both params are documented, so baseline is 3; the description adds a genuinely non-obvious constraint not present in the schema ('exactly one of `id` or `url`'), which clarifies how the two optional params relate.

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

Purpose5/5

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

States a specific verb and resource ('Returns the trivia IMDb lists for a title'), which cleanly distinguishes it from siblings like imdb_title_goofs, imdb_title_quotes, and imdb_title_keywords. An agent can tell exactly what content it retrieves.

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 description gives one concrete usage rule ('Pass exactly one of `id` or `url`'), which is useful, but it offers no when-to-use context or named alternatives among the many imdb_title_* siblings. Usage is implied rather than guided.

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