Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Lemmy posts

lemmy_posts_list
Read-onlyIdempotent

List Lemmy posts from a specified instance, optionally for one community and in a chosen order. Use cursor pagination to retrieve additional result pages.

Instructions

List Lemmy posts, optionally for one community, in the order asked for. Requires instance. Returns a list (use cursor when paginated).

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

Input Schema

NameRequiredDescriptionDefault
nsfwNoInclude NSFW posts. Default: false, as on the instance.
pageNoPage number, 1 to 100. Default: 1. An instance refuses pages past 100. Lemmy pages by number over a live order, so new or re-ranked items can shift a row onto the next page. Remove repeats by `id`.
sortNoOrder. `Scaled` and `Controversial` are refused by 0.18 instances.
limitNoRows per page, 1 to 50. Default: 10.
scopeNo`local` reads only this instance's own items; `all` includes federated items the instance has seen. Default: the endpoint's own listing.
cursorNoPass `page.nextCursor` from the previous response to get the next page. It only works with the same filters; do not send it with `page`.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
instanceYesRequired. The Lemmy instance, e.g. `lemmy.world`. A URL on the instance is also accepted. Ids and counts belong to this instance.
communityNoThe community whose posts to list, e.g. `technology` or `canada@lemmy.ca`.
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 readOnly, idempotent, non-destructive, and open-world behavior, so safety is covered. The description adds only that instance is required and that paginated results should use the cursor, both of which are already spelled out in the schema. Nothing is said about instance-specific ids/counts or paging drift.

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?

A single lead sentence followed by two short clarifying fragments; front-loaded with purpose and free of filler. Minor redundancy in restating required parameters that the schema already enforces.

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 11 parameters, no output schema, and nuanced pagination behavior, the definition leans almost entirely on the rich schema. It gives a terse return hint ('Returns a list') but omits the post shape, the local/all federation distinction, and the page-100 refusal, all of which matter for correct invocation.

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 already documents sort, nsfw, page/limit caps, cursor/page mutual exclusion, and scope. The description adds no syntax or format detail beyond 'Requires instance', which the schema already marks as required. 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 Lemmy posts') plus the key optional narrowing ('optionally for one community') and ordering, which separates it reasonably well from siblings like lemmy_user_posts_list or lemmy_communities_list. It never explicitly names a sibling it is not, so it stops short of 5.

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?

'Optionally for one community, in the order asked for' implies the scope and sort use cases, but there is no explicit when-to-use versus when-not guidance and no named alternative (e.g. user-specific post listings). Usage is inferable rather than stated.

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