Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

imdb_charts

Fetch normalized rows from public IMDb title charts, including top-rated, most-popular, English, and lowest-rated movies or TV shows, with optional row limits.

Instructions

IMDb title charts. Returns normalized rows from public IMDb title charts. Chart values: top_rated_movies, top_rated_tv_shows, most_popular_movies, most_popular_tv_shows, top_rated_english_movies, lowest_rated_movies.

Input Schema

TableJSON 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

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It does convey that data is 'public' and output is 'normalized rows,' which signals a read-only, transformed response. However, it does not mention auth needs, rate limits, pagination, or what normalization entails, leaving meaningful gaps.

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-loads the core behavior before listing chart values. The opening phrase 'IMDb title charts' is somewhat redundant with the tool name and the second sentence, but overall the structure is efficient and scannable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple, parameters are fully documented in the schema, and the description covers the chart options. However, there is no output schema and the description does not specify what fields or structure the normalized rows contain, leaving the agent to infer the return shape.

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%, with the chart enum and limit parameter already documented, so the baseline is 3. The description redundantly lists the chart values that already appear in the enum, adding no new semantic detail about how parameters interact with the output.

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?

The description clearly states the resource ('IMDb title charts') and the action ('Returns normalized rows'), and it enumerates the exact chart values available. It is specific and easy to understand, though it does not explicitly differentiate itself from sibling IMDb tools beyond the chart-specific resource.

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?

The description implies usage by listing the available chart values and stating it returns public IMDb charts, but it does not provide explicit guidance on when to use this tool versus alternatives or when not to use it. There are no exclusions or alternative tool references.

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