Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List popular Letterboxd members

letterboxd_members_popular_list
Read-onlyIdempotent

Fetch the first 30 popular Letterboxd members and their public counts to discover active community profiles for research or outreach.

Instructions

List the first 30 popular Letterboxd members, with their public counts. 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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "letterboxd_members_popular_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

B3.4/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 safety is fully covered structurally. The description adds real value by disclosing the hard cap of 30 results and that public counts are included, but it omits pagination/ordering details and gives only 'Returns a list' about the payload.

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 with the cap and contents front-loaded; nothing is buried. The trailing 'Returns a list' is near-redundant given the leading 'List ...', costing a small amount of precision.

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?

For a simple read-only listing tool with rich annotations, the essentials (scope, cap, included counts) are present. Without an output schema, though, an agent still learns nothing about the list item shape beyond 'public counts', leaving a modest gap.

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% and the three parameters are meta-parameters (context, llm_model, conversation_id) already fully documented in the schema. The description adds nothing parameter-specific, 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 ... popular Letterboxd members') plus an explicit scope ('first 30'), which separates it from user-scoped siblings like letterboxd_user_followers_list. It never names an alternative, though, so differentiation is inferred from the scope rather than stated.

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?

The 'popular members' framing implies a discovery/browse use case, but there is no explicit when-to-use or when-not-to-use guidance and no pointer to user_followers_list or user_get for member lookups. Usage is only implied.

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