Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Lemmy post

lemmy_post_get
Read-onlyIdempotent

Fetch a specific Lemmy post by ID to get its community, cross-posts, and moderators; requires an instance and can locate the post from a comment ID.

Instructions

Get one Lemmy post with its community, cross-posts and moderators. Requires instance.

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

Input Schema

NameRequiredDescriptionDefault
idNoPost id on the chosen instance, e.g. `53910627`.
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.
commentIdNoFind the post a comment belongs to.
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

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds that the response is enriched with community, cross-posts, and moderators, which is useful beyond annotations, but it says nothing about failure modes such as an unknown id or an unreachable instance.

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?

Two short sentences with the capability first and the prerequisite second; no filler or redundancy.

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?

For a 6-parameter read tool with no output schema, the description gives the highlighted return contents and the key prerequisite. It omits error behavior and does not clarify how `id` and `commentId` interact, leaving gaps an agent would have to infer from the schema alone.

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 documents every parameter including the id-vs-commentId distinction and the context/llm_model/conversation_id plumbing. The description only restates the `instance` requirement that the schema already marks as required, adding no new parameter meaning.

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 and resource ("Get one Lemmy post") and enumerates the expanded content returned: community, cross-posts, and moderators. The singular "one post" inherently separates it from list-oriented siblings like lemmy_posts_list, though no sibling is named explicitly.

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

Usage Guidelines2/5

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

The only guidance is the prerequisite "Requires `instance`." Nothing says when to prefer this over lemmy_posts_list or lemmy_post_comments_list, nor when to resolve a post via `commentId` instead of `id`.

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