Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Lemmy federated instances

lemmy_instances_list
Read-onlyIdempotent

List federated Lemmy instances for a given source, with software, version, and delivery status, to assess federation and block relationships.

Instructions

List Lemmy federated instances with software, version and delivery status. Requires source. 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": {
      "source": "<source>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "lemmy_instances_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number. Default: 1. The federated directory has no 100-page ceiling.
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`.
sourceYesRequired. The Lemmy instance whose federation table to return, e.g. `fed.dyne.org`. A URL on the instance is also accepted.
blockedNo`true` returns the instance's block list; `false` (default) returns the domains it federates with.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
softwareNoSoftware to keep, matched case-insensitively; `all` keeps every domain. Default: `lemmy`.
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.
activeSinceNoOnly domains whose last successful federation delivery is at or after this time, as an ISO 8601 date or time (such as `2026-01-31`) or epoch seconds. A time with no zone is UTC.
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 safety is covered without the description. The description adds only that results are paginated with a cursor, while the richer behavioral rules (blocked list vs federation list, activeSince cutoff, conversation_id sequencing) 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 tightly packed sentences with the required parameter front-loaded and no filler. The parenthetical cursor note is slightly awkward but earns its place.

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 filtered list tool with no output schema and full schema coverage, the description gives enough to call it correctly: what comes back, what is mandatory, and how paging works. It stops short of explaining the blocked/software toggles, but those are covered in 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%, so every parameter including the protocol fields (context, llm_model, conversation_id) is already documented. The description only restates that `source` is required and that cursor is for pagination, adding no meaning 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?

States a specific verb+resource ('List Lemmy federated instances') and names the fields returned (software, version, delivery status). It does not distinguish itself from the sibling lemmy_instance_get, so the list-vs-single-instance boundary is left implicit.

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?

Says `source` is required and hints at cursor pagination, which gives some usage context. It never states when to prefer this over lemmy_instance_get or lemmy_search, nor when to use the blocked/software filters, so alternates are only implied.

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