Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

imdb_title_release_info

Retrieve IMDb release dates and alternate titles for a movie or show using its IMDb ID or URL.

Instructions

IMDb title release info. Returns the release dates and alternate titles IMDb lists for a title. Pass exactly one of id or url. Releases have a country, date and note; alternate titles have a country, title and type. Both lists are often shorter than total and alternate_titles_total.

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

A3.6/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 disclosure burden. It usefully notes that both lists are 'often shorter than total and alternate_titles_total' (a truncation caveat), which is genuine behavioral context, but it omits any mention of read-only nature, auth needs, rate limits, or actual return envelope.

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?

Content is front-loaded with the resource, then the return shape, then the parameter constraint, then a caveat. Slightly redundant opening title restates the tool name, keeping it from a full 5, but overall it is tight and earn-its-place.

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?

There is no output schema, so describing the release and alternate-title field shapes and the truncation caveat does useful work. For a simple two-param read tool this is nearly complete, though a note on which identifier is preferable would close the last gap.

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 the baseline is 3, but the description adds a real constraint the schema does not express: the two mutually exclusive parameters must be supplied exactly one at a time. That mutual-exclusivity rule is meaningful value beyond the schema's plain optional strings.

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 (returns release dates and alternate titles for an IMDb title) and even enumerates the fields of each list. It is unambiguous on its own, but it never contrasts itself against the many sibling imdb_title_* tools, so sibling differentiation is left implicit.

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 usage directive is 'Pass exactly one of `id` or `url`', which governs invocation but not when to pick this tool over imdb_title, imdb_title_awards, etc. Usage is implied by the returned content rather than stated as a when-to-use rule.

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