List Lemmy federated instances
lemmy_instances_listList 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
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number. Default: 1. The federated directory has no 100-page ceiling. | |
| limit | No | Rows per page, 1 to 50. Default: 10. | |
| cursor | No | Pass `page.nextCursor` from the previous response to get the next page. It only works with the same filters; do not send it with `page`. | |
| source | Yes | Required. The Lemmy instance whose federation table to return, e.g. `fed.dyne.org`. A URL on the instance is also accepted. | |
| blocked | No | `true` returns the instance's block list; `false` (default) returns the domains it federates with. | |
| context | Yes | Describe the user's underlying goal in one sentence, not the tool you are calling. | |
| software | No | Software to keep, matched case-insensitively; `all` keeps every domain. Default: `lemmy`. | |
| llm_model | Yes | The 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. | |
| activeSince | No | Only 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_id | No | Echo 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. |