Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

imdb_name_awards

Fetch awards IMDb lists for a person by IMDb name ID or URL. Returns event, year, category, win or nomination, recipients, and related titles.

Instructions

IMDb name awards. Returns the awards IMDb lists for a person. Pass exactly one of id or url. Each row has the event, year, category, win or nomination result, award name, recipients and related titles. total is the count IMDb lists, and has_more is true when fewer rows are returned.

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
Behavior4/5

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

With no annotations and no output schema, the description carries the full burden and does well: it enumerates the returned row fields (event, year, category, win/nomination, award name, recipients, related titles) and explains total and has_more. It stops short of pagination mechanics or auth requirements, so not a 5.

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-loaded with the purpose, then the invocation rule, then the return shape — four tight sentences with no redundancy.

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 output schema exists, and the description compensates by describing the row structure and the total/has_more flags. Only pagination instructions and access prerequisites are missing.

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%, but the description adds a constraint the schema does not encode: required is empty, yet the description mandates exactly one of id or url. That mutual-exclusivity rule is genuinely additive information.

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 verb and resource: 'Returns the awards IMDb lists for a person.' The 'for a person' scope distinguishes it from the title-awards sibling, but it never names an alternative explicitly, which keeps it just short of a 5.

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

Usage Guidelines2/5

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

The only guidance is 'Pass exactly one of id or url,' which is an invocation constraint rather than when-to-use context. There is no statement of when this tool is preferred over imdb_name, imdb_name_credits, or imdb_title_awards, and no prerequisites.

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