Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Lemmy post comments

lemmy_post_comments_list
Read-onlyIdempotent

List comments on a Lemmy post or replies to a specific comment by providing the instance; paginate with a cursor for larger threads.

Instructions

List comments on one Lemmy post, or the replies to one comment. 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_post_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. `Controversial` is refused by 0.18 instances.
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`.
postIdNoPost id on the chosen instance, e.g. `53910627`.
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.
parentIdNoList this comment and its replies instead of the whole post. Walk a deeper branch by passing one of its reply ids here.
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 read-only, idempotent, open-world and non-destructive, so the safety profile is covered. The description adds only that it returns a list and cursor-based pagination exists, while the more important behaviors (page/cursor mutual exclusion, page-100 ceiling, duplicate rows across pages) live in the schema rather than here.

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 compact sentences, front-loaded with the action and followed by the prerequisite and return shape. No filler, though the parenthetical about cursor is a fragment that assumes schema context.

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 10-parameter tool with no output schema, the definition covers the prerequisite and return shape but says nothing about postId-vs-parentId selection or what a comment record contains. The rich schema compensates substantially, keeping this at minimum-viable rather than poor.

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 parameters are fully documented in structured form and the baseline is 3. The description reinforces that `instance` scopes ids and that cursor applies to pagination, but adds no syntax or format detail beyond the schema.

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?

Names a specific verb and resource ("List comments on one Lemmy post") and adds a second mode ("replies to one comment"), which is enough to distinguish it from broad listing siblings like lemmy_comments_list. It stops short of naming any 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?

Conveys the two usage modes and the hard prerequisite ("Requires `instance`"), so context is implied. It never states when to pick this over lemmy_comments_list or lemmy_user_comments_list, leaving the agent to infer routing.

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