Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Lemmy instance

lemmy_search
Read-onlyIdempotent

Search Lemmy posts, comments, communities, users, or exact URLs on a specified instance to locate relevant discussions, content, and accounts.

Instructions

Search Lemmy posts, comments, communities, users or exact URLs; All and Comments can take longer. Requires instance and query. Returns a list (use cursor when paginated).

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>",
      "query": "<query>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "lemmy_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1 to 100. Default: 1. An instance refuses pages past 100. Lemmy pages by number over a live order, so new or re-ranked items can shift a row onto the next page. Remove repeats by `id`.
sortNoOrder. `Scaled` and `Controversial` are refused by 0.18 instances.
typeNo`Posts` (default), `All` (every kind), `Comments` (comment text), `Communities`, `Users` or `Url` (posts linking to an exact URL). `All` and `Comments` can take much longer than the other kinds.
limitNoRows per page, 1 to 50. Default: 10.
queryYesRequired. Search term, 1 to 300 characters, in any language. Required, never empty and no control characters.
scopeNo`local` reads only this instance's own items; `all` includes federated items the instance has seen. Default: the endpoint's own listing.
authorNoRestrict to one author, by username.
cursorNoPass `page.nextCursor` from the previous response to get the next page. It only works with the same filters; do not send it with `page`.
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.
communityNoCommunity name, e.g. `technology`, or `technology@lemmy.world` to resolve a community on another instance. Prefer the community's home instance for counts.
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.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds real context beyond that: the latency asymmetry of the All and Comments search types, the required-parameter constraint, and the cursor-based pagination contract. It does not describe result ordering or error behavior, which keeps it from a 5.

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 clauses, front-loaded with the resource scope, then the caveat, then the return/pagination note. No filler sentences, though the semicolon-chained first clause is slightly dense.

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

Completeness3/5

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

With 13 parameters, 4 of them required, and no output schema, the description gives only a one-line return hint ('Returns a list'). It never mentions the required context, llm_model, or conversation_id parameters, so an agent relying on the description alone would be surprised by validation failures. The rich schema compensates, but the description leaves meaningful gaps for a tool of this complexity.

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 explains every parameter including page/cursor interaction, sort enums, and scope. The description adds only a restatement that instance and query are required, and notably omits that context and llm_model are also required. Baseline 3 is appropriate when the schema carries the semantic load.

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 (Search) and a specific resource set (Lemmy posts, comments, communities, users, exact URLs), which lets an agent distinguish it from the sibling list/get tools like lemmy_posts_list or lemmy_community_get. It stops short of naming any sibling or explicitly stating the boundary, so it is clear but not maximally differentiating.

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 gives a performance hint ('All and Comments can take longer') and a pagination hint ('use cursor when paginated'), but never says when to choose this search over the sibling listing tools or when not to use it. Usage is implied by the type enumeration in the schema rather than stated in the description.

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