Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

letterboxd_popular

Fetch a popularity-ranked Letterboxd film chart, filtered by day, week, month, year, genre, or decade, and return film titles, slugs, and URLs.

Instructions

Get a Letterboxd popularity-ranked film chart. Returns a Letterboxd film chart ranked by popularity. Omit period for all-time, or set day, week, month or year. genre takes a genre slug, decade a value like 2010s, and limit defaults to 10 with a max of 50. Each film has its slug, title and Letterboxd URL.

Input Schema

NameRequiredDescriptionDefault
genreNoGenre slug filter
limitNoMax films, default 10, max 50
decadeNoDecade filter, e.g. 2010s
periodNoPopularity window, omit for all-time

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / period / enum
      Added value: +[
+  "day",
+  "week",
+  "month",
+  "year"
+]
  2. Addedv1.5.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses the default and max for `limit` and lists the returned fields (slug, title, URL), which is real added context, but says nothing about authorization, rate limits, or whether the chart is cached/mutable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Front-loaded and reasonably compact, but the opening two sentences are redundant — 'Get a Letterboxd popularity-ranked film chart' is immediately restated as 'Returns a Letterboxd film chart ranked by popularity', wasting one of only three sentences.

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, the description steps in to list returned fields, and all four optional parameters are addressed with defaults and the enum's all-time option. It is nearly complete for a simple 4-param read tool, missing only cross-tool routing.

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 baseline is 3. The description largely restates the schema ('genre takes a genre slug', 'limit defaults to 10 with a max of 50') and adds only the minor example value `2010s` for `decade`.

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 ('Get a Letterboxd popularity-ranked film chart') that distinguishes it from letterboxd_film, letterboxd_search and letterboxd_film_similar. However, it never names those siblings or explains how this chart differs from them, so the differentiation is implicit rather than explicit.

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?

Offers operational guidance on one parameter ('omit `period` for all-time, or set day/week/month/year'), which implies when each mode applies, but gives no guidance on when to choose this chart tool over letterboxd_search or letterboxd_film, and no exclusions.

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