Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

imdb_name_videos

Fetch public IMDb person video metadata and thumbnail URLs using an IMDb name ID or profile URL. Returns no playback URLs; limit up to 100.

Instructions

IMDb name video metadata. Returns public person video metadata and thumbnail URLs only; playback URLs and media manifests are never returned. IMDb caps the upstream slice at 100 and provides no usable continuation cursor, so total can exceed returned rows and has_more reports that condition. Limit defaults to 50 and clamps to 100. Pass exactly one of id or url.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoIMDb name id
urlNoAbsolute https://www.imdb.com/name/<id>/ URL
limitNoRows to return, default 50, max 100

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.7/5.0
Behavior5/5

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

The description discloses important behavioral traits beyond annotations: it never returns playback URLs, the upstream slice is capped at 100 with no continuation cursor, `total` can exceed returned rows, `has_more` reports that condition, and limit defaults to 50 and clamps to 100. This is rich behavioral context that an agent needs to interpret results correctly.

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 compact and information-dense. Every sentence adds value: what is returned, what is not returned, pagination behavior, limit defaults, and input constraints. It is well-structured with the most important information front-loaded.

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?

The description is complete for an agent to call this tool correctly. It covers the input requirements, output scope, pagination caveats, and limit behavior. No output schema exists, but the description adequately explains what will be returned (metadata and thumbnail URLs) and what won't.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all three parameters. The description adds the constraint that exactly one of `id` or `url` must be passed, which is valuable, but it doesn't add much beyond that since the schema already covers the parameter meanings.

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 clearly states the tool returns IMDb name video metadata and thumbnail URLs, explicitly excluding playback URLs and media manifests. It distinguishes itself from sibling tools like imdb_name, imdb_name_credits, and imdb_title_videos by focusing on person video metadata.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states the input constraint: 'Pass exactly one of `id` or `url`.' It also explains the limit behavior and the upstream cap, giving clear guidance on when to use this tool and how to handle pagination limitations.

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