Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

imdb_name

Fetch an IMDb person's profile by ID or URL to retrieve biography, birth and death dates, birthplace, professions, image, and known-for titles with year and credit category.

Instructions

IMDb name detail. Returns an IMDb person's profile. Pass exactly one of id (such as nm0634240) or url. The response has the name, biography, birth and death dates, birth place, professions, image and a known-for list of titles with year and credit category.

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A3.7/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 burden. It usefully describes the returned profile fields, acting as partial output documentation, but it does not cover auth needs, rate limits, or error behavior when neither/both id and url are supplied.

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 short sentences, front-loaded with purpose, then parameter constraint, then return contents. Every sentence earns its place and nothing is padded.

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?

No annotations or output schema exist, so the description's summary of returned fields is important. It is nearly complete for a lookup tool, though it could better distinguish when to use this profile endpoint versus the many sibling IMDb name tools.

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 already 100%, so baseline is 3. The description adds meaningful semantics by requiring exactly one of id or url and gives an example id format (nm0634240), which is not fully captured by the schema's empty required list.

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 resource and action: returns an IMDb person's profile. It is clearly different from siblings like imdb_name_awards or imdb_name_images by focusing on the core name detail, but it does not explicitly name those alternatives.

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 implies usage by saying it returns a person's profile and by giving the exact-one-of id/url constraint. However, it does not state when to use this tool instead of related siblings such as imdb_name_credits or imdb_name_awards.

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