Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Letterboxd member watchlist

letterboxd_user_watchlist_list
Read-onlyIdempotent

Fetch the first 28 films on a Letterboxd member's public watchlist by username. Use it to see what films someone plans to watch; private watchlists return restricted.

Instructions

List the first 28 films on a Letterboxd member's public watchlist; a private one answers restricted. Requires username. Returns a list.

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "letterboxd_user_watchlist_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint. The description adds real behavior beyond them: a 28-item cap, and the fact that a private watchlist returns `restricted` rather than an error. Pagination continuation beyond the first 28 is not addressed.

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?

One compact sentence-cluster front-loads the scope, then the private-list behavior, then the requirement and return type. Nothing is padded, though the 'Returns a list' tail is near-redundant with 'List'.

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?

For a simple read-only listing tool with full annotation coverage and full schema descriptions, the definition covers scope, the private-list edge case, and the return shape. Only the pagination story for lists longer than 28 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 coverage is 100%, so the schema already documents username, context, llm_model and conversation_id in detail. The description only restates that `username` is required, adding no new meaning; the 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?

The description uses a specific verb and resource ('List the first 28 films on a Letterboxd member's public watchlist') and bounds the scope precisely. It does not name a sibling such as letterboxd_user_films_list to contrast with, so it stops short of a 5.

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 by the word 'public watchlist', but there is no explicit when-to-use or when-not-to-use guidance, and no alternative is named for retrieving a full film list or another member's data.

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