Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Lemmy user posts

lemmy_user_posts_list
Read-onlyIdempotent

List a Lemmy user's posts from a given instance, ordered by New, Old, or top time windows, with pagination to retrieve more results.

Instructions

List Lemmy posts by one user, in the order asked for. Requires instance and username. 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>",
      "username": "<username>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "lemmy_user_posts_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
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. Only `New`, `Old` and the time-window tops; `TopAll` and `Hot` are not offered.
limitNoRows per page, 1 to 50. Default: 10.
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.
usernameYesRequired. Username, e.g. `dessalines`, or `user@lemmy.ml` to resolve a user on another instance.
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.5/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. The description adds that the result is a list and that a cursor applies when paginated, which is modest extra context; it does not discuss rate limits, instance quirks, or what a returned post contains.

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, front-loaded with the action and scope, with the requirement called out immediately after. The trailing "(use cursor when paginated)" is largely redundant with the schema's cursor documentation, keeping it from a 5.

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?

For a 9-parameter read tool with 100% schema coverage and full annotations, the description supplies the essentials an agent needs to select and call it, and the pagination details live in the schema. With no output schema, the one-line "Returns a list" is thin on return shape, but not blocking.

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 every parameter — page, sort, limit, cursor, instance, username, context, llm_model, conversation_id — is already documented in detail. The description only repeats the two required fields and gestures at sort, adding essentially no meaning beyond the schema, so the baseline of 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 a scope qualifier ("by one user"), which distinguishes it from the general post-listing and comment-listing siblings without naming them. It stops short of explicitly routing the agent away from `lemmy_posts_list` or `lemmy_user_comments_list`, so it is clear but not fully differentiated.

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?

"Requires `instance` and `username`" gives a precondition, and "in the order asked for" implies sort is honored, but there is no explicit when-to-use vs. when-not guidance and no named alternative. Usage is only implied by the tool's scope 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