Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Lemmy community

lemmy_community_get
Read-onlyIdempotent

Retrieves 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

NameRequiredDescriptionDefault
idNoCommunity id on the chosen instance, e.g. `2478`.
nameNoCommunity name, e.g. `technology`, or `technology@lemmy.world` to resolve a community on another instance. Prefer the community's home instance for counts.
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

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the bar is lower. The description still adds useful behavioral context by naming what comes back — counts, active users and moderators — which matters because there is no output schema; it could have gone further on whether an unknown community errors or returns empty.

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 action and payload, with the prerequisite tacked on at the end. Minimal waste, though the `instance` requirement is already marked required in the schema, making the second sentence slightly redundant.

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 simple read-one lookup with no output schema, the description gives the essential shape of the response and the key prerequisite. The remaining gap is that it does not distinguish lookup by id versus by `name`/fully-qualified name, which the schema handles but the description never signals.

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 the schema already documents `instance`, `id`, `name`, and the telemetry params in detail, including the home-instance hint for accurate counts. The description's only parameter statement ('Requires `instance`') repeats the schema and adds no new meaning, so 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 ('Get one Lemmy community') and names the returned payload (counts, active users, moderators), which cleanly separates it from the plural `lemmy_communities_list` sibling. It stops short of explicitly naming any alternative, so sibling differentiation is implied rather than stated.

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?

The only usage constraint given is 'Requires `instance`', which is a prerequisite rather than a when-to-use rule. Nothing tells the agent when to pick this over `lemmy_communities_list`, `lemmy_instance_get`, or `lemmy_search`; the choice must be inferred from the singular/plural contrast.

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