Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Lemmy instance moderation log

lemmy_modlog_list
Read-onlyIdempotent

List Lemmy moderation log entries filtered by action kind, community, or moderator, and paginate results with a cursor to audit moderation activity on a given instance.

Instructions

List the Lemmy moderation log by kind, community or moderator. Requires instance. 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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "lemmy_modlog_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoKind of moderation action. `all` returns every kind in one answer; with it, `limit` applies to each kind and is at most 10. Omit it with `community` to get every kind for that community, up to 20 each.
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`.
limitNoRows per kind, 1 to 50. Default: 10. With `kind=all`, or with no kind or community, at most 10; with a community but no kind, at most 20. One page can carry up to 15 times the limit across the kinds.
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.
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.
communityIdNoOnly this community's moderation log, by its numeric id.
modPersonIdNoOnly actions taken by this moderator or administrator.
otherPersonIdNoOnly actions whose subject is this person.
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.7/5.0
Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds only that an instance is required, that it returns a list, and that a cursor handles pagination — useful but thin; the real pagination semantics (page drift, cursor vs page exclusivity) live in the schema, not here.

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 sentences, front-loaded with the verb and resource, zero padding. The trailing '(use cursor when paginated)' restates what the cursor parameter description already says, so a small amount of waste remains.

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 an 11-parameter tool with no output schema, the definition is minimal: it never mentions the required `context`, `llm_model`, or `conversation_id` contract, nor the mutual exclusivity of `cursor` and `page`. Adequate to identify the tool, insufficient to call it correctly without reading the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description goes slightly beyond by naming the three filtering dimensions (kind, community, moderator) and flagging the required `instance`, giving the agent a mental model of the filter set before opening the schema.

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?

Specific verb+resource: 'List the Lemmy moderation log', plus the three filter axes (kind, community, moderator) and the mandatory `instance`. No sibling modlog tool exists, so there is nothing to disambiguate against, which keeps it just short of a 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?

'by kind, community or moderator' and 'Requires `instance`' imply how to narrow a query, and the cursor hint implies paging. However, it gives no when-to-use/when-not guidance, no alternative tools, and omits the schema's important caveats (kind=all caps the limit at 10, community-only caps at 20).

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