Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Letterboxd review

letterboxd_review_get
Read-onlyIdempotent

Fetch a Letterboxd review by username and film slug to retrieve its full text, rating, watched date, tags, likes, and rewatch number.

Instructions

Get a Letterboxd review with its full text, rating, watched date, tags, likes and rewatch number. 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_review_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesRequired. Letterboxd film slug: letters, digits and hyphens, e.g. `parasite-2019`. Input is lowercased. Required, no default; 1 to 200 characters.
entryNoEntry number from the review URL (`/{username}/film/{slug}/{entry}/`). Omit it for the viewing without a number; `rewatch` tells you whether it is a rewatch.
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

B3.4/5.0
Behavior3/5

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

The annotations already declare this a read-only, idempotent, open-world, non-destructive operation, so safety disclosure is handled. The description adds a useful list of returned fields, which goes beyond the annotations. However, it says nothing about missing reviews, private or deleted reviews, or the role of `entry` and `conversation_id`, all of which affect how the agent behaves.

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 sentences, front-loaded with the core action and the returned data, then the input requirements. No filler and nothing wasted.

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?

The tool is a simple read, the parameters are fully described in the schema, and the description compensates for the absence of an output schema by enumerating the returned fields. Only the multi-entry and `conversation_id` protocol nuances are left to the schema, which is acceptable.

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 baseline is 3. The description restates that `username` and `slug` are required, but that is already in the schema, and it omits `entry`, `context`, `llm_model`, and `conversation_id`, none of which it explains further. It adds no meaning beyond what the schema already documents.

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 gives a specific verb ('Get') and a specific resource ('a Letterboxd review'), and it enumerates what a review contains (full text, rating, watched date, tags, likes, rewatch number). This separates it well from sibling resources such as film, list, or user lookups without needing to name them.

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 description states the required inputs but gives no guidance on when to use this tool instead of alternatives such as letterboxd_user_reviews_list or letterboxd_film_get. An agent must infer the difference from tool names alone, so this dimension has clear gaps.

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