Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

imdb_title_filming_locations

Retrieve the filming locations IMDb lists for a movie or TV title by passing its IMDb ID or URL, and get each location's text, optional note, and total count.

Instructions

IMDb title filming locations. Returns the filming locations IMDb lists for a title. Pass exactly one of id or url. Each location has its text and an optional note. total is the count IMDb lists, has_more shows when the list is cut short, and a title with none returns an empty list with total 0.

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.2/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and mostly succeeds: it describes the shape of each returned location (text plus optional note), the meaning of `total` and `has_more`, and the empty-list-with-total-0 edge case. It does not discuss permissions or rate limits, but this is a public read endpoint, so that gap is minor.

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?

Front-loads the resource identity, then the parameter rule, then the return shape. Four short sentences with no filler; every clause conveys something actionable.

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, yet the description documents the return structure (location text/note, total, has_more, empty-list behavior) well enough to call and interpret it. Only finer details like error responses or truncation thresholds 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 baseline would be 3. The description adds a genuinely useful constraint beyond the schema: exactly one of `id` or `url` must be supplied, a mutual-exclusivity rule the flat schema does not encode.

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 filming locations IMDb lists for a title') and is self-evidently distinct from the many imdb_title_* siblings (trivia, goofs, quotes). An agent can tell exactly which endpoint this is without opening the schema.

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?

Provides an invocation constraint ('Pass exactly one of `id` or `url`'), but that is parameter-level guidance rather than when-to-use/when-not guidance. There is no explicit routing to an alternative or statement of preconditions, so usage is only implied.

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