Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Letterboxd member reviews

letterboxd_user_reviews_list
Read-onlyIdempotent

Fetch a Letterboxd member's first 12 reviews with ratings, likes, spoiler flags, and review text by username to analyze viewing opinions and sentiment.

Instructions

List the first 12 reviews of a Letterboxd member, with rating, likes, spoiler flag and text. 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_reviews_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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description contributes one genuinely useful behavioral fact beyond them: the result is capped at the first 12 reviews, which tells the agent there is no full-history retrieval here. It does not say whether paging is possible or how ordering works.

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?

Two tight sentences with the scope and returned fields front-loaded. The closing 'Returns a list' is close to redundant for a tool already named as a list operation, a small wasted clause.

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 usefully names the returned fields (rating, likes, spoiler flag, text) and the 12-item cap, covering the essentials for a read-only list tool. The only gap is the lack of any note on ordering or whether more than 12 can be reached.

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%, including the context, llm_model and conversation_id parameters, so the schema carries the parameter burden. The description only restates that username is required, adding no meaning beyond the schema; 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 gives a specific verb and resource ('List the first 12 reviews of a Letterboxd member') plus the returned fields, so the agent knows exactly what comes back. It does not explicitly distinguish itself from close siblings such as letterboxd_review_get or letterboxd_user_diary_list, leaving that inference to the agent.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative. The agent must infer from the name alone that this is the member-review route rather than the diary, films, or single-review routes.

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