Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Letterboxd member statistics

letterboxd_user_stats_get
Read-onlyIdempotent

Retrieves a Letterboxd member's statistics by username; returns partial header data when the profile is restricted.

Instructions

Get a Letterboxd member's statistics, or the partial header when they are restricted. Requires username.

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_stats_get"
  }
}

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.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, so the description's real contribution is the disclosure that restricted members yield only a partial header instead of full statistics. That is a concrete behavioral trait an agent would otherwise misread as an error or empty result. It stops short of describing what statistic categories are included.

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?

A single front-loaded sentence with no filler, and the required-parameter note comes last where it belongs. Minor deduction because "partial header" is dropped in without explanation, leaving the reader to parse jargon.

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

Completeness3/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 carries the burden of describing the return value, yet it never says what statistics are returned or their shape. For a read-only stats endpoint that is a moderate gap, though the restricted-account behavior partially compensates.

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% and the username constraints (lowercasing, max 64 chars, no default) are fully documented in the schema, so baseline 3 applies. The description's "Requires `username`" merely restates the schema and adds nothing about the required context/llm_model/conversation_id parameters.

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 member's statistics") and adds the restricted-account variant. It does not name a sibling alternative, but the scope is narrow enough that an agent can separate it from the letterboxd_user_*_list tools.

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 only implied: the description says what it returns and that `username` is required, but never says when to prefer this over letterboxd_user_get or the activity/diary/list tools. An agent must infer that stats means aggregate counts rather than per-item 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