Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

imdb_title_keywords

Retrieve IMDb plot keywords for a title using an IMDb ID or URL. Returns each keyword's text and search link, with the total keyword count listed.

Instructions

IMDb title keywords. Returns the plot keywords IMDb lists for a title. Pass exactly one of id or url. Each keyword has its text and an IMDb search URL for that keyword. 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.1/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 does add real behavioral context: each keyword carries text plus an IMDb search URL, and the caveat that 'total' is what IMDb lists so a short list is normal on popular titles preempts a false 'missing data' reading. It stops short of confirming read-only status or pagination behavior.

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?

Front-loaded with the core purpose and roughly four tight sentences with no padding. The opening fragment 'IMDb title keywords' mildly duplicates the tool name but costs almost nothing.

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?

For a simple two-parameter read tool with no annotations and no output schema, the description covers the input rule and the shape/quirks of the return values, which is what an agent needs. Only pagination and explicit read-only confirmation are absent.

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 is 3, but the description adds the mutual-exclusivity rule ('Pass exactly one of id or url') that the schema does not enforce since it lists zero required parameters. That is genuine value beyond the structured fields.

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?

Specific verb+resource: 'Returns the plot keywords IMDb lists for a title.' This clearly separates it from the dense cluster of imdb_title_* siblings (quotes, goofs, trivia, ratings) an agent could otherwise confuse it with.

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?

Usage guidance is limited to the parameter constraint ('Pass exactly one of id or url'). There is no explicit when-to-use/when-not-to-use or routing to an alternative sibling for related info, so selection context is only implied by the name.

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