Skip to main content
Glama

Lemmy

by io.github.pipeworx-io

Search

search
Read-onlyIdempotent

Full-text search across a Lemmy instance (default lemmy.world) for posts, comments, communities, or users matching query q. Filter by type (Posts/Comments/Communities/Users), listing (All/Local), and sort order.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYes
pageNo
sortNo
limitNo
type_NoAll | Comments | Posts | Communities | Users | Url
instanceNo
listing_typeNoAll | Local | Subscribed

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
postsNoSearch results: posts
type_NoSearch type (All, Comments, Posts, Communities, Users, Url)
usersNoSearch results: users
commentsNoSearch results: comments
communitiesNoSearch results: communities

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: +[
+  {
+    "q": "rust programming"
+  },
+  {
+    "instance": "lemmy.world",
+    "limit": 15,
+    "q": "python",
+    "sort": "TopMonth",
+    "type_": "Posts"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Response from Lemmy API /search endpoint",
+  "properties": {
+    "comments": {
+      "description": "Search results: comments",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "communities": {
+      "description": "Search results: communities",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "posts": {
+      "description": "Search results: posts",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "type_": {
+      "description": "Search type (All, Comments, Posts, Communities, Users, Url)",
+      "type": "string"
+    },
+    "users": {
+      "description": "Search results: users",
+      "items": {
+        "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, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context: it is a full-text search, uses lemmy.world as default instance, and supports filtering by type, listing, and sort. This goes beyond the annotations without contradicting 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 compact—two sentences—and front-loads the primary purpose with the query parameter. Every clause adds relevant information about scope, default instance, and filter options, making it highly efficient.

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?

The tool has 7 parameters and an output schema, so the description doesn't need to detail return values. It covers the core invocation (required `q`), default instance, and available filters. The main gap is the lack of explicit mention of pagination parameters and alternatives, but for a search tool this is reasonably complete.

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?

Schema description coverage is only 29%, so the description must compensate. It clarifies `q` as the query, `instance` defaults to lemmy.world, and explains `type_`, `listing_type`, and `sort` in prose. While `page` and `limit` are not detailed, they are standard pagination parameters and the description covers the most semantically important fields.

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 the tool performs full-text search across a Lemmy instance for posts, comments, communities, or users matching the query `q`. It specifies the default instance and distinguishes itself from sibling tools like `search_within` by covering cross-type search.

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 description implies usage for searching across multiple content types and mentions filtering by type, listing, and sort order. However, it does not explicitly state when to prefer this tool over alternatives like `search_within` or the dedicated `posts`/`comments` endpoints, so the guidance is implicit rather than explicit.

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