Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Lemmy user

lemmy_user_get
Read-onlyIdempotent

Retrieve a Lemmy user's profile with post and comment counts, moderator roles, and latest activity. Specify the instance to fetch accurate data for that user.

Instructions

Get one Lemmy user with counts, moderator roles and latest activity. 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_user_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoUser id on the chosen instance, e.g. `34`.
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.
usernameNoUsername, e.g. `dessalines`, or `user@lemmy.ml` to resolve a user on another instance.
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
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 a modest amount beyond that – the returned data shape (counts, mod roles, latest activity) and the instance-scoping constraint – but says nothing about behavior when a user is absent, whether id or username takes precedence, or cross-instance resolution cost.

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 compact sentences, front-loaded with the operation and the returned fields, with the required-parameter note after. Nothing is padded, though the trailing 'Requires `instance`' sentence is largely redundant with the schema.

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?

A single-entity read with complete schema coverage, full annotation set and no output schema – the description supplies all an agent needs to select and call it. Return contents are summarized and the required instance is called out, so remaining gaps are only niceties.

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 id, username, instance and the context/model parameters are all documented in the schema itself; baseline 3 applies. The description's 'Requires `instance`' merely restates a required field and adds no meaning about the id-vs-username choice that the schema already explains.

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 user') and enumerates what comes back: counts, moderator roles, latest activity. That distinguishes it in substance from the sibling list tools (lemmy_user_comments_list, lemmy_user_posts_list) without naming them, so it falls just short of the explicit 5.

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?

Usage is only implied by the resource name – an agent can infer this is for fetching a single user profile. There is no explicit when-to-use, no statement of when to prefer the comments/posts list siblings instead, and no note about prerequisites other than the instance hint.

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