Lemmy

Community

community

Read-onlyIdempotent

Fetch metadata for a specific Lemmy community by name (e.g. "asklemmy") or numeric id from the specified instance. Returns description, icon, subscriber count, and moderators.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`instance`	No
`name_or_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description
`counts`	No	Community statistics (subscribers, posts, comments)
`community`	No	Community object with id, name, title, description
`moderators`	No	List of community moderators

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "name_or_id": "asklemmy@lemmy.world"
+  },
+  {
+    "instance": "lemmy.world",
+    "name_or_id": "12345"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Response from Lemmy API /community endpoint",
+  "properties": {
+    "community": {
+      "description": "Community object with id, name, title, description",
+      "type": "object"
+    },
+    "counts": {
+      "description": "Community statistics (subscribers, posts, comments)",
+      "type": "object"
+    },
+    "moderators": {
+      "description": "List of community moderators",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedMay 18, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already establish read-only and idempotent behavior. The description adds value by stating what the tool returns (description, icon, subscriber count, moderators) and clarifying it fetches from a specified instance. It does not mention error cases, but the added context is sufficient for a simple read operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, well-structured sentence that front-loads the purpose, includes examples, and summarizes return fields. Every word contributes meaning with no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is low-complexity: it fetches metadata for one community. The description covers purpose, input semantics, and key output fields, while annotations cover safety. The output schema exists, so the description is complete enough for an agent to invoke and interpret the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides no parameter descriptions, so the description carries the full burden. It clearly explains that name_or_id can be a community name like 'asklemmy' or a numeric id, and that instance is the source instance. The schema examples reinforce this, making the parameter semantics unambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Fetch metadata') and clearly identifies the resource: a specific Lemmy community by name or numeric id from a specified instance. This distinguishes it from the sibling 'communities' tool by focusing on a single community's metadata.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides clear context for when to use the tool (fetching a specific community's metadata) and gives input format examples. It does not explicitly exclude alternatives like 'communities' for listing, but the singular/plural distinction strongly implies the appropriate use case.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Lemmy tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.