Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

imdb_search

Search IMDb titles by query and retrieve up to 20 results with details like year, type, image, and lead cast. Returns empty list if no matches.

Instructions

IMDb title search. Searches IMDb titles by query, returning up to limit rows (default 10, max 20). Each result has the title id, title, URL, year, title type, image and a description holding the lead cast. A query with no matches returns an empty results list.

Input Schema

NameRequiredDescriptionDefault
limitNoRows to return, default 10, max 20
queryYesSearch query

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, the description carries the full burden and does disclose real behavior: default and max row counts, the exact result fields returned, and that a no-match query yields an empty `results` list. It omits auth/permission needs and rate-limit behavior, which keeps it from 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.

Conciseness4/5

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

Three tight sentences, front-loaded with purpose then the pagination rule then the return shape. No filler, though the field enumeration sentence is slightly dense.

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, so the description's enumeration of returned fields (id, title, URL, year, type, image, lead-cast description) plus the empty-result case is genuinely load-bearing. Only permission/error semantics are unaddressed for a simple read tool.

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 description coverage is 100%, so the schema already documents both `query` and `limit`. The description repeats the default-10/max-20 limits without adding syntax or constraint detail beyond the schema, so the baseline 3 applies.

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 ('IMDb title search', 'Searches IMDb titles by `query`'), so the agent knows it is a search not a detail fetch. However, it does not differentiate itself from the near-identical sibling `imdb_search_title`, leaving that routing decision to the schema.

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 is implied by the query/limit contract, but the description never states when to prefer this over `imdb_search_title` or the detail tools `imdb_title`/`imdb_name`, nor any exclusions. Adequate but leaves alternative selection entirely to inference.

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