Skip to main content
Glama

Crawlora MCP

letterboxd_popular

Read-only

Letterboxd popularity-ranked film chart.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
genreNoOptional genre slug filter, e.g. mystery.
limitNoMax films, default 10, max 50.
decadeNoOptional decade filter, e.g. 2010s.
periodNoPopularity window: day, week, month, year, or omit for all-time.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and network scope are covered. The description adds nothing beyond that – notably it does not explain its relationship to the period/popularity-window parameters (day/week/month/year/all-time), which is the most behaviorally interesting aspect of this tool.

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?

A single front-loaded sentence with no filler. It is efficient, though minimal to the point of under-delivering on the tool's most distinctive behavior.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. What is missing is any hint about how the popularity window interacts with results and what the chart represents relative to Letterboxd's other film endpoints, leaving the description adequate but thin for a chart tool with four filters.

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 genre, limit, decade and period semantics. The description adds no syntax, formatting or cross-parameter interaction details (e.g., how genre and decade combine), so 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 resource (Letterboxd film chart) and that it is popularity-ranked, which distinguishes it from keyword search. It does not, however, differentiate itself from other browse/chart siblings such as letterboxd_film_similar or potential trending tools elsewhere in the catalog.

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 a browse-the-chart use case but gives no explicit when-to-use guidance, no statement of when to prefer letterboxd_search or letterboxd_member, and no prerequisites. Usage context is inferred from the name and the word 'chart' rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources