Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Letterboxd member recent activity

letterboxd_user_activity_list
Read-onlyIdempotent

Retrieve a Letterboxd member's recent activity—watches, reviews, lists, and stories—by username to see what they have watched, written, or shared recently.

Instructions

List a Letterboxd member's recent activity: watches, reviews, lists and stories. 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_activity_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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. Beyond them the description adds only 'Returns a list' — no mention of ordering, how many items are returned, whether the feed is paginated, or whether a private profile yields an error or empty result.

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 short sentences, front-loaded with what is listed and what is required; nothing is padded. The trailing 'Returns a list' is marginally redundant with the leading 'List', keeping it just short of a 5.

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?

There is no output schema, so the description is the only place the return shape could be explained, and 'Returns a list' is the bare minimum. For a read-only aggregate feed this is adequate but leaves the agent guessing about item structure, page size and ordering.

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 all four parameters including context, llm_model and conversation_id are already documented in the schema. The description repeats the username requirement without adding format, case-handling or default information beyond the schema, so the baseline of 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?

States a specific verb and resource ('List a Letterboxd member's recent activity') and enumerates the activity types returned: watches, reviews, lists and stories. That is clearer than the bare name, but it does not distinguish this aggregate feed from siblings like letterboxd_user_diary_list or letterboxd_user_reviews_list, whose content overlaps the enumerated items.

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 cue is 'Requires `username`', which is a parameter constraint, not a routing rule. There is no statement of when to prefer this aggregate activity feed over the per-type siblings (diary, reviews, lists), and no exclusions or prerequisites.

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