Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

imdb_title_company_credits

Fetch IMDb company credits for a title by ID or URL, returning production companies and distributors with names, links, and qualifier notes.

Instructions

IMDb title company credits. Returns the company credits IMDb lists for a title, in sections such as production companies and distributors. Pass exactly one of id or url. Each company has its name, URL and a qualifier note. total is the count IMDb lists, so a short list is normal on popular titles.

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, the description carries the full burden and adds meaningful behavioral context: it describes the return structure (sections, company name, URL, qualifier note) and explains that `total` is the count IMDb lists, so short lists are expected. It does not mention authentication, rate limits, or error behavior, but materially supplements what structured fields provide.

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?

The description is front-loaded with the operation and return shape, followed by the input rule and a useful caveat about short lists. Every sentence earns its place and there is no redundant filler.

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?

For a low-complexity, two-parameter read tool with no output schema, the description is complete enough: it explains what is returned, how the input works, and what the `total` value means. An agent has all it needs to invoke correctly.

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 would be 3. The description adds important meaning beyond the schema by stating that exactly one of `id` or `url` must be passed, which the schema itself does not enforce because both properties are optional and there is no oneOf constraint.

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?

The description states a specific verb and resource: it returns IMDb company credits for a title, with sections such as production companies and distributors. This distinguishes it from other IMDb title tools like imdb_title_credits (cast/crew) and imdb_title (general title data).

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?

It gives the key invocation constraint 'Pass exactly one of `id` or `url`', but does not explain when to choose this tool over sibling IMDb title tools or when either input form is preferable. Usage is implied by the tool name and description rather than explicitly 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