Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Letterboxd list

letterboxd_list_get
Read-onlyIdempotent

Fetch a Letterboxd list by username and slug to retrieve its description, tags, likes, clones, and first 100 films. Use it to inspect or analyze a curated film list.

Instructions

Get a Letterboxd list with its description, tags, likes, clones and first 100 films. Requires username and slug.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "username": "<username>",
      "slug": "<slug>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "letterboxd_list_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesRequired. Letterboxd list slug: letters, digits, `-`, `_`, `.`, `~` or `:`, e.g. `letterboxds-top-500-films`. Required, no default; 1 to 200 characters.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
usernameYesRequired. Letterboxd username: letters, digits and `_`, e.g. `davidehrlich`. Input is lowercased. Required, no default; at most 64 characters.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered. The description adds two genuinely useful behavioral facts beyond that: the response includes list metadata (description, tags, likes, clones) and is truncated to the first 100 films. It does not say whether the remaining films are reachable elsewhere or how truncation should be communicated, so it is not fully transparent.

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?

Two short sentences, front-loaded with the verb and resource, then the return shape, with zero filler. Nothing could be removed without losing information.

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 must carry the return shape, and it does list the main fields plus the 100-film cap. The gap is that it never explains how an agent should obtain films beyond the first 100 or handle a private/missing list, which matters for a read tool whose results are intentionally partial.

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 coverage is 100%, so username, slug, context, llm_model and conversation_id are all documented in the schema itself. The description only repeats that username and slug are required and adds no meaning for the identity/conversation parameters, which is the baseline-3 case when the schema does the work.

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 list') and enumerates the payload returned (description, tags, likes, clones, first 100 films). It stops short of naming the sibling it complements, e.g. letterboxd_user_lists_list for discovering a list versus this tool for fetching one by username+slug.

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?

The only usage statement is 'Requires `username` and `slug`', which restates the schema's required fields rather than telling the agent when to pick this over letterboxd_user_lists_list or letterboxd_members_popular_list. No exclusions, no prerequisites about lists being public, and no guidance on what to do when a list is private or nonexistent.

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