Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List latest Lemmy comments

lemmy_comments_list
Read-onlyIdempotent

Fetch recent Lemmy comments from a specified instance or community, with sorting, paging, and cursor support for paginated results.

Instructions

List the latest Lemmy comments across an instance or community. 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_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.
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.
communityNoCommunity name, e.g. `technology`, or `technology@lemmy.world` to resolve a community on another instance. Prefer the community's home instance for counts.
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, openWorld and non-destructive, so the safety profile is covered. The description adds only that results come back as a list and that cursor is the pagination mechanism when results are paged. It says nothing about federation behavior, empty results, or how paging over a live ranking can reshuffle rows (which the schema mentions instead).

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 purpose and scope. The trailing 'Returns a list (use cursor when paginated)' is slightly redundant with the fully documented `cursor` and `page` schema properties, but costs little.

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 no output schema and ten parameters, the description is thin, but the 100%-covered schema compensates for parameter detail and the annotations cover safety. It is adequate for a simple listing tool, though it leaves result shape and pagination semantics entirely to the schema.

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 each of the ten parameters carries substantive documentation, so the schema does the heavy lifting. The description only restates that `instance` is required and gestures at cursor usage, adding no meaning beyond the structured fields.

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 the latest Lemmy comments') plus the scope ('across an instance or community'), which implicitly distinguishes it from post-scoped or user-scoped comment listings. It never names lemmy_post_comments_list or lemmy_user_comments_list, so the differentiation is left to inference.

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 only implied: the agent can infer this is for browsing recent comments broadly rather than for a specific post or user. There is no explicit when-to-use/when-not guidance, no mention of how `sort`, `scope`, `page` or `cursor` should drive the choice, and no named alternative.

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