Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Lemmy user comments

lemmy_user_comments_list
Read-onlyIdempotent

Lists a Lemmy user's comments with sort and pagination controls. Use it to review a specific user's comment history on any instance, ordered by new, old, or top time windows.

Instructions

List Lemmy comments 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_comments_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.6/5.0
Behavior3/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 only that it returns a list and to use the cursor when paginated, which the schema already documents, so it adds little beyond structured data.

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, front-loaded with the core action and scope, with zero redundant wording.

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 nine-parameter paginated list tool with no output schema, the description plus the rich schema cover what an agent needs to call it correctly. It could say more about the returned list shape, but the schema carries most of the burden.

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 all nine parameters are fully documented in the schema, including sort, page, limit, and cursor semantics. The description merely restates the two required parameters, adding no meaning beyond the schema; 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 with scope: 'List Lemmy comments by one user.' This distinguishes it from the general comment-list siblings by the per-user scope, though it does not name an alternative explicitly.

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 implied by the per-user scope, and it notes the required `instance` and `username`. There is no explicit when-to-use vs. when-not guidance or named alternative such as the general comments list.

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