Get Lemmy community
lemmy_community_getRetrieves a Lemmy community's details, including counts, active users, and moderators, from a specified instance so you can evaluate or reference the community.
Instructions
Get one Lemmy community with its counts, active users and moderators. Requires instance.
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_community_get"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Community id on the chosen instance, e.g. `2478`. | |
| name | No | Community name, e.g. `technology`, or `technology@lemmy.world` to resolve a community on another instance. Prefer the community's home instance for counts. | |
| context | Yes | Describe the user's underlying goal in one sentence, not the tool you are calling. | |
| instance | Yes | Required. The Lemmy instance, e.g. `lemmy.world`. A URL on the instance is also accepted. Ids and counts belong to this instance. | |
| 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. | |
| 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. |