Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Letterboxd film

letterboxd_film_get
Read-onlyIdempotent

Retrieve a Letterboxd film's details by slug, including synopsis, cast, crew, releases, rating, similar films, and popular reviews.

Instructions

Get a Letterboxd film's identity, synopsis, cast, crew, releases, rating, similar films and popular reviews. Requires slug.

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": {
      "slug": "<slug>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "letterboxd_film_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesRequired. Letterboxd film slug: letters, digits and hyphens, e.g. `parasite-2019`. 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.6/5.0
Behavior3/5

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

Annotations already establish readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description's one real addition is that the response is a large multi-section bundle (cast, crew, releases, similar films, reviews), hinting at payload weight, but it says nothing about rate limits, failure modes, or whether the film must exist.

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 sentences with zero filler; the payload description is front-loaded and the requirement statement trails it. Nothing is redundant or padded.

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?

Since there is no output schema, the enumeration of returned sections does real work in telling the agent what it will receive, and the annotations cover the safety profile. What remains thin is guidance on selecting this tool over the many sibling getters, which matters given how many 'get' tools exist in this catalog.

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 both the slug format and the context/llm_model/conversation_id plumbing are already documented in the schema. The description adds no meaning beyond repeating that a slug is required and says nothing about the three non-slug parameters, so the 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?

Specific verb ('Get') plus resource ('a Letterboxd film') followed by an explicit enumeration of the returned sections (identity, synopsis, cast, crew, releases, rating, similar films, popular reviews). This clearly separates it from letterboxd_review_get or letterboxd_list_get at the resource level, though it never names those siblings to reinforce the distinction.

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: an agent can infer it should call this when it needs film-level metadata, and the enumerated return fields help that decision. There is no explicit when-not guidance (e.g., 'for individual reviews use letterboxd_review_get'), and the 'Requires `slug`' line merely restates the schema's required field rather than adding a precondition.

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