Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Letterboxd person or studio films

letterboxd_person_films_list
Read-onlyIdempotent

Lists films from a Letterboxd person or studio filmography using a role and slug, with studios returning their first 24 titles. Use it to retrieve filmography entries as a structured list.

Instructions

List the films in a Letterboxd person or studio filmography; a studio returns its first 24. Requires role and slug. 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": {
      "role": "<role>",
      "slug": "<slug>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "letterboxd_person_films_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYesRequired. Crew role the person is filed under, e.g. `director`, `actor`, `producer`, `editor`, `cinematography` or `studio`.
slugYesRequired. Letterboxd person or studio slug: letters, digits and hyphens, or `contributor:` with digits, e.g. `bong-joon-ho`. Input is lowercased. Required, no default; 1 to 200 characters.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
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.8/5.0
Behavior4/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. The description adds a genuinely non-obvious behavioral fact beyond them: a studio result is capped at the first 24 films, which tells the agent results can be truncated. It does not say whether person filmographies are similarly capped or how large a response can be.

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 short clauses with zero padding, the resource and scope front-loaded, followed by the truncation caveat. Every sentence earns its place.

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 full schema coverage and strong annotations, the description mostly suffices, and the studio cap is a useful addition. Gaps remain around whether person filmographies are truncated, what a returned film entry contains, and any pagination behavior, none of which has an output schema to fall back on.

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 an enum for `role` and format rules for `slug`, so the schema carries the parameter burden; the baseline of 3 applies. The description only restates that `role` and `slug` are required, adding no syntax or semantics beyond what is already documented.

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 states a specific verb and resource ('List the films in a Letterboxd person or studio filmography') and scopes it to person/studio rather than user lists, which meaningfully separates it from letterboxd_user_films_list. It stops short of naming any sibling explicitly as an alternative.

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 by the purpose statement plus the 'Requires `role` and `slug`' note; there is no explicit when-to-use versus when-not-to-use guidance or pointer to alternatives such as a film lookup or user film list. An agent can infer the context, but nothing steers it away from a wrong sibling.

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