Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Lemmy communities

lemmy_communities_list
Read-onlyIdempotent

List local or federated communities from a specified Lemmy instance, sorted by the requested order, with pagination support for browsing results.

Instructions

List Lemmy communities, local or federated, 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_communities_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nsfwNoInclude NSFW communities. 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.
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 readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered structurally. The description only adds that it returns a list and the cursor hint for pagination, both of which the schema's cursor parameter already explains more thoroughly.

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 verb and resource. "Requires `instance`" partially restates the schema's required list, which is minor waste, but nothing else pads the text.

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?

Adequate for a 10-parameter read-only list tool with no output schema and full schema coverage, since the heavy behavioral detail lives in parameter descriptions. It never addresses the conversation_id/llm_model plumbing or what a returned list contains, leaving some gaps for a call this involved.

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 the schema already documents page/shift behavior, sort enum caveats, scope semantics, and cursor usage in detail. The description adds nothing beyond repeating that `instance` is required, so the 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 communities") plus scope ("local or federated") and ordering. It does not distinguish itself from siblings like lemmy_community_get or lemmy_search, so an agent must infer the boundary from those tools' names rather than being told.

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?

Gives an implied usage cue ("use cursor when paginated") and a prerequisite ("Requires `instance`"), but never states when to prefer this over lemmy_community_get or lemmy_search, nor when not to use it.

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