Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

imdb_name_images

Fetch image metadata from an IMDb person's media index by name ID or profile URL, returning original URL, dimensions, caption, credited people, with optional type filters and limits.

Instructions

IMDb name images. Returns image metadata from a person's media index, including the original image URL, dimensions, caption and credited people. Filter by image type with type, which accepts a single value or a comma-separated list of: behind_the_scenes, event, poster, product, production_art, publicity, still_frame, unknown. Omit type to return every type. Limit defaults to 50 and clamps to 1000. Pass exactly one of id or url.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoIMDb name id
urlNoAbsolute https://www.imdb.com/name/<id>/ URL
typeNoImage type filter, single value or comma-separated list
limitNoRows to return, default 50, max 1000

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral disclosure burden. It discloses what is returned, how the `type` filter behaves, the limit clamping behavior, and the exclusivity of `id`/`url`. This gives an agent a reliable model of the tool's behavior without requiring schema inspection.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded, stating the core purpose before enumerating filters and limits. Every sentence carries useful information, though the opening 'IMDb name images' is a mild redundancy with the tool name.

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?

Given the tool's moderate complexity, the description covers the essential invocation constraints, filtering semantics, and return content. No output schema exists, but the description compensates by naming the returned metadata fields. Nothing critical is missing for an agent to call this tool 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 schema already documents each parameter. The description adds value by clarifying that `type` accepts a comma-separated list, that omitting `type` returns all types, and that exactly one of `id` or `url` must be provided—details that go beyond the schema definitions.

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 that the tool returns image metadata for a person from IMDb, listing the exact kind of data included (original URL, dimensions, caption, credited people). This distinguishes it from sibling tools like imdb_title_images or imdb_name_videos by explicitly scoping it to a person's media index.

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

Usage Guidelines4/5

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

The description provides clear operational guidance: use `type` for filtering, omit it for all types, limit defaults/clamps, and pass exactly one of `id` or `url`. It does not explicitly name alternatives or state when-not-to-use, but the context is clear enough for an agent to select this tool appropriately.

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