Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Mastodon post boosts and likes

mastodon_post_reactions_list
Read-onlyIdempotent

List the accounts that boosted or favourited a Mastodon post by providing its public URL and selecting boosts or favourites; use the returned cursor to fetch more pages.

Instructions

List the accounts that boosted or favourited a Mastodon post. Requires url and kind. 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": {
      "url": "<url>",
      "kind": "<kind>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "mastodon_post_reactions_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Public URL of a post, e.g. `https://mastodon.social/@Gargron/117555039933723776`. The server in the URL is the server asked, because post ids belong to a server.
kindYesRequired. `boosts` lists who boosted the post, `favourites` who favourited it.
limitNoItems per page, 1 to 80. Default: 40.
cursorNoPass `page.nextCursor` from the previous response to get the next page.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is handled. The description usefully adds that results are a paginated list consumed via cursor, but says nothing about rate limits, auth expectations, empty results, or how likes and boosts interleave.

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?

Three short sentences, front-loaded with the action, then prerequisites, then return shape and pagination. No filler; slightly terse rather than verbose.

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 simple read-only listing tool with full schema coverage and rich annotations, the essentials are present, including return shape. It omits the analytics/conversation parameters and any guidance on the open-world server dependency described in the `url` schema, leaving those entirely to the schema.

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 100%, so the baseline is 3, but the description reinforces the two required parameters and, importantly, the pagination contract for `cursor` ('use cursor when paginated'), which is the one piece of call-flow semantics an agent must not miss.

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?

Names a specific verb and resource ('List the accounts that boosted or favourited a Mastodon post'), which is precise enough to separate it from comment/edits/context siblings on the same platform. It doesn't explicitly name an alternative tool, so it stops short of 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?

Implied usage only: the caller learns it needs `url` and `kind`, and that pagination uses a cursor. There is no statement of when to prefer this over `mastodon_post_get` or related listing tools, and no exclusions or preconditions beyond the required parameters already in the schema.

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