Skip to main content
Glama

Lemmy

by io.github.pipeworx-io

Post

post
Read-onlyIdempotent

Fetch a single Lemmy post by numeric id from the specified instance (default lemmy.world). Returns title, body, author, score, comment count, and community.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
instanceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
postNoPost object with id, name, url, body, etc.
countsNoPost statistics (upvotes, downvotes, comments)
creatorNoPost creator user object
communityNoCommunity object

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": 12345
+  },
+  {
+    "id": 67890,
+    "instance": "lemmy.world"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Response from Lemmy API /post endpoint",
+  "properties": {
+    "community": {
+      "description": "Community object",
+      "type": "object"
+    },
+    "counts": {
+      "description": "Post statistics (upvotes, downvotes, comments)",
+      "type": "object"
+    },
+    "creator": {
+      "description": "Post creator user object",
+      "type": "object"
+    },
+    "post": {
+      "description": "Post object with id, name, url, body, etc.",
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds useful behavioral context by stating the default instance and enumerating the return fields (title, body, author, score, comment count, and community), which goes beyond what annotations provide and does not contradict them.

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, focused sentence that front-loads the action and includes only necessary details. Every word earns its place, with no redundancy.

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?

For a simple fetch tool with two parameters, strong annotations (readOnlyHint, idempotentHint), and a known output schema, the description covers all essential aspects: what it fetches, the default instance, and the returned fields. It is complete and actionable for an agent.

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

Parameters4/5

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

With schema description coverage at 0%, the description compensates by clarifying that 'id' is numeric and by explaining the 'instance' parameter with a default value (lemmy.world). The examples further illustrate parameter usage, making the semantics clear.

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 clearly states it 'Fetch a single Lemmy post by numeric id' with a specific verb and resource. It distinguishes from sibling 'posts' by emphasizing 'single' post and the numeric id requirement, making its purpose unambiguous.

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?

The description provides clear context for when to use the tool: when you have a numeric id and need a single post. It specifies the default instance (lemmy.world) but does not explicitly mention alternatives or exclusions relative to sibling tools like 'posts'.

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

All Lemmy toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation2/5

Many tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, and validate_claim all answer factual questions, while bet_research, polymarket_edges, polymarket_arbitrage, and polymarket_fill_risk all analyze prediction markets. The Lemmy tools are distinct from the Pipeworx tools, but within each cluster an agent could easily select the wrong tool despite lengthy descriptions.

Naming Consistency2/5

Naming conventions are mixed: single nouns (post, community, site), verb_noun patterns (list_subscriptions, resolve_entity, generate_llms_txt), and ad-hoc names (ask_pipeworx, forget, recall). There is no consistent verb_noun or noun-only pattern across the set, making it hard to predict tool names.

Tool Count2/5

38 tools is excessive for a server named 'Lemmy' where only 7 tools (comments, communities, community, post, posts, search, site) actually relate to Lemmy. The vast majority of tools belong to an unrelated Pipeworx data platform, creating a severe scope mismatch and making the server feel bloated and unfocused.

Completeness2/5

For the Lemmy domain, the tools cover read-only browsing (list posts, view post, list communities, fetch community, comments, search, site metadata) but completely lack write operations like posting, commenting, voting, or moderation. The Pipeworx tools are extensive but do not compensate for the primary domain's gaps since the server is ostensibly about Lemmy.

Resources