Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

letterboxd_search

Search Letterboxd for films, people, lists, and tags by query. Filter to films and set a result limit to find titles, profiles, user lists, or tags quickly.

Instructions

Search Letterboxd. Searches Letterboxd for films, people, lists and tags by q, required. type can be set to film to return films only; limit defaults to 10 with a max of 50. Fields vary by result type: films carry slug and year, people carry slug and role, lists carry owner, and tags carry only a title and URL.

Input Schema

NameRequiredDescriptionDefault
qYesSearch query
typeNoOptional result type filter
limitNoMax results, default 10, max 50

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / type / enum
      Added value: +[
+  "film"
+]
  2. Addedv1.5.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well by disclosing per-result-type field shapes (films: slug/year; people: slug/role; lists: owner; tags: title/URL) and the limit default (10) and ceiling (50). It does not discuss auth, rate limits, or error behavior, but for a read-only search those are less critical. The result-shape detail is the key behavioral value.

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 front-loaded with the core action and proceeds logically through entity scope, parameters, and result shape. Every sentence contributes; the only minor cost is density from backtick-heavy inline code. It is efficient and easy to scan.

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

Completeness5/5

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

For a low-complexity, three-parameter search tool with full schema coverage but no output schema, this description is complete enough. It defines scope, filtering, pagination bounds, and return-field variation by type, which is exactly what is missing from the structured data. Nothing an agent needs in order to invoke or interpret it correctly is absent.

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 `q`, `type` (with enum), and `limit` (default 10, max 50). The description restates these facts without adding syntax, format, or interaction semantics beyond what is in the schema. Baseline 3 is appropriate.

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 opens with a specific verb and resource ('Search Letterboxd') and immediately enumerates the four searchable entity types (films, people, lists, tags), which distinguishes it from single-entity siblings like letterboxd_film or letterboxd_person. An agent can identify exactly what this tool does without opening the schema.

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: use this when you have a query for any Letterboxd entity, and optionally narrow to films via `type`. However, it never names or contrasts with alternatives like letterboxd_popular, letterboxd_member, or letterboxd_film, so the agent receives no explicit routing guidance. This is adequate but leaves selection between search and specific-fetch tools to inference.

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