Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

imdb_charts

Fetch IMDb title rankings across top-rated, popular, or lowest-rated movies and TV shows, returning rank, rating, and credits in JSON.

Instructions

IMDb title charts. Returns an IMDb title chart, chosen with chart: top_rated_movies (default), top_rated_tv_shows, most_popular_movies, most_popular_tv_shows, top_rated_english_movies or lowest_rated_movies. limit sets the rows (default 25, max 250). Each title has its rank, id, year, rating, rating count and credits.

Input Schema

NameRequiredDescriptionDefault
chartNoIMDb chart
limitNoRows to return, default 25, max 250

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / chart / enum
      Added value: +[
+  "top_rated_movies",
+  "top_rated_tv_shows",
+  "most_popular_movies",
+  "most_popular_tv_shows",
+  "top_rated_english_movies",
+  "lowest_rated_movies"
+]
  2. Addedv1.16.0

TDQS

A3.7/5.0
Behavior4/5

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

No annotations are provided, so the description carries full burden: it discloses the returned fields (rank, id, year, rating, rating count, credits) and the limit bounds (default 25, max 250). It does not mention auth, pagination beyond limit, or rate limits, but for a read-only chart endpoint it is reasonably transparent.

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 the resource, then the selector enum with its default, then the output shape. Every sentence carries information; only the leading 'IMDb title charts.' fragment is mildly redundant with the following sentence.

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?

With no output schema and no annotations, the description must explain return values, and it does list the fields each title carries. For a zero-required-param chart tool this is largely complete, missing only pagination/ordering details.

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% and the schema already documents the enum and the 'default 25, max 250' bounds, so the description largely restates structured data. Baseline 3 applies; it adds no syntax or edge-case semantics beyond the schema.

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 an IMDb title chart' — and enumerates the six chart variants, so an agent knows exactly what it gets. It does not name or differentiate itself from the numerous imdb_title_* siblings, which keeps it 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 Guidelines3/5

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

Usage is implied through the enumerated chart options and the noted default (top_rated_movies), so an agent can infer when it applies. There is no explicit when-to-use vs alternatives guidance and no exclusions, e.g. pointing to imdb_search_title for ad-hoc lookups rather than rankings.

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