Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Letterboxd member following

letterboxd_user_following_list
Read-onlyIdempotent

Fetch the first 25 accounts a Letterboxd member follows using their username to inspect following relationships for social or film analysis.

Instructions

List the first 25 accounts a Letterboxd member follows. 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_following_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 elsewhere. The description adds genuinely new behavior — a hard cap of the first 25 accounts and a list-shaped return — but is silent on whether the 25 is a page size, whether deeper results are reachable, ordering, and error behavior for unknown/private usernames.

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?

Three short sentences with the scope (25, follows) and the required input front-loaded before the return note; nothing is buried. "Returns a list" is only marginally informative given the tool name, so it is slightly wasteful rather than harmful.

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 and four parameters, the description should carry more of the return contract than "Returns a list" — e.g. what fields each followed account exposes or how truncation at 25 manifests. It is adequate to make a correct single call, but not complete enough for an agent to reason about result coverage or pagination.

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%, so the schema fully documents `username`, `context`, `llm_model` and `conversation_id`, including format, lowercasing and the conversation_id echo protocol. The description only repeats that `username` is required and adds no format, casing or defaulting detail beyond the schema, so 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?

States a specific verb and resource ("List the first 25 accounts a Letterboxd member follows") and names the input it needs. The word "follows" implicitly separates it from the followers-list sibling, but the description never names that sibling or otherwise explicitly differentiates itself from the many other 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 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; the closest thing is the bare "Requires `username`" note, which is a parameter constraint rather than usage direction. An agent must infer from the tool name alone whether to pick this over letterboxd_user_followers_list or letterboxd_user_activity_list.

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