Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

letterboxd_film_similar

Find films similar to a given Letterboxd movie. Returns Letterboxd's recommended similar films using public data.

Instructions

Get films similar to a Letterboxd film. Returns films Letterboxd recommends as similar to the given film. Credential-free public Letterboxd data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesLetterboxd film slug
limitNoMax films, default 10, max 50
Behavior3/5

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

No annotations are provided, so the description carries the burden. It adds useful context with 'Credential-free public Letterboxd data,' indicating no authentication required. However, it does not disclose behavior for invalid slugs, rate limits, or output format, leaving gaps.

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

Conciseness5/5

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

The description is extremely concise with two sentences. The key action ('Get films similar') is front-loaded. Every sentence adds value without redundancy.

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?

Given the tool has 2 parameters and no output schema, the description is adequate but not complete. It explains the basic purpose and credential-free nature, but does not describe the output format (e.g., expected fields like slug or title) or handle edge cases. The limit parameter is noted in schema, but pagination context is missing.

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 does not add additional meaning beyond the schema; it repeats that the tool returns similar films but does not elaborate on slug format or limit behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Get films similar to a Letterboxd film' and 'Returns films Letterboxd recommends as similar to the given film.' It uses specific verbs and resources, distinguishing it from siblings like letterboxd_film or letterboxd_popular, which serve different functions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No explicit guidance is provided on when to use this tool versus alternatives. The description implies usage when you need similar films, but it does not mention when not to use it or provide context on choosing between siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Crawlora-org/crawlora-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server