Skip to main content
Glama

Lemmy

by io.github.pipeworx-io

Posts

posts
Read-onlyIdempotent

List Lemmy posts (federated Reddit-alternative; ActivityPub) from a community or feed. Sort by Active / Hot / New / TopDay / TopWeek / etc. Returns post title, body, author, upvotes, comment count. Use for federated open-source discussion forum content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
sortNoActive | Hot | New | Old | TopDay | TopWeek | TopMonth | TopYear | TopAll | MostComments | NewComments
limitNo
type_NoAll | Local | Subscribed
instanceNo
communityNoCommunity name (e.g. "asklemmy@lemmy.world") or id.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
postsNoList of posts

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: +[
+  {
+    "community": "asklemmy@lemmy.world",
+    "limit": 10,
+    "sort": "Hot"
+  },
+  {
+    "instance": "lemmy.world",
+    "page": 1,
+    "sort": "New",
+    "type_": "Local"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Response from Lemmy API /post/list endpoint",
+  "properties": {
+    "posts": {
+      "description": "List of posts",
+      "items": {
+        "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"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds behavioral context by listing return fields (title, body, author, upvotes, comment count) and sort modes, which are not fully captured in annotations. It does not repeat annotation info or contradict it.

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 four short, front-loaded sentences. Each sentence conveys distinct information: what the tool lists, sort options, returned fields, and use case. There is no redundancy or filler, making it extremely concise for the information provided.

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 list tool with 6 parameters and an output schema, the description covers the essential aspects: purpose, feed/community source, sort options, and return fields. The output schema handles return structure, so the description doesn't need to explain that. It misses explicit guidance on instance and type_ filters, but the tool is simple enough that the overall description is sufficient.

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 50%, with sort, type_, and community having descriptions. The description adds meaning for community ('from a community or feed') and sort ('Active / Hot / New / TopDay / TopWeek / etc.'), but leaves page, limit, and instance semantics unexplained beyond their types. It partially compensates for the gap but not fully.

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 'List' with a clear resource 'Lemmy posts', and details that it works from a community or feed. It distinguishes itself from siblings like 'post' (singular) and 'comments' by focusing on listing multiple posts. Mention of sort options and return fields further sharpens the purpose.

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 by stating 'Use for federated open-source discussion forum content' and implies when to use it for browsing posts from a community or feed. However, it does not explicitly mention alternatives like 'post' for a single post or 'comments' for comment listings, which would have made the guidance stronger.

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