Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

imdb_title_similar

Fetch IMDb 'More like this' recommendations for any title by passing its IMDb ID or URL, returning similar titles with ratings, runtime, and images.

Instructions

IMDb similar titles. Returns the titles in IMDb's More like this recommendations for a title. Pass exactly one of id (such as tt0111161) or url. Each title has its id, name, URL, year, type, runtime, content rating, rating, rating count and image.

Input Schema

NameRequiredDescriptionDefault
idNoIMDb title id
urlNoAbsolute IMDb title URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully enumerates the returned fields (id, name, URL, year, type, runtime, content rating, rating, rating count, image), which compensates for the absent output schema. However, it discloses nothing about read-only nature, auth, or rate limits, leaving gaps for an annotation-free tool.

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 sentences, front-loaded with purpose, then the input constraint, then the return shape. No wasted words and each sentence contributes distinct information.

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?

With no output schema, the description appropriately describes the returned fields, and it documents both parameters and their exclusivity. For a simple read lookup it is essentially complete; only behavioral details like auth/rate limits are absent.

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 value beyond the schema: it specifies the mutual exclusivity constraint ('exactly one of') and provides a concrete id example (tt0111161) that the schema lacks.

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 titles from IMDb's 'More like this' recommendations for a given title. The purpose is unambiguous and distinct from siblings like imdb_title or imdb_title_ratings. It does not explicitly name a sibling it differs from, but the resource is clearly the recommendations list.

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 guidance on when to use this tool versus alternatives such as imdb_title_connections or letterboxd_film_similar. The only directive, 'Pass exactly one of id or url,' is a parameter constraint rather than a when-to-use rule, so usage must be inferred from the name.

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