Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Mastodon post edit history

mastodon_post_edits_list
Read-onlyIdempotent

Lists every saved version of a Mastodon post from its public URL, returning the edit history so you can review changes.

Instructions

List every saved version of a Mastodon post. Requires url. Returns a list.

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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only 'Returns a list', which is thin: it says nothing about ordering, whether the current version is included, or how many versions come back. For a history tool, the ordering and inclusion of the current revision are the details an agent actually needs.

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 purpose, with no wasted clauses. 'Returns a list' is low-value filler but the overall shape is efficient and easy to scan.

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?

This is a simple read-only list tool with a fully documented schema and no output schema, so the description does not need to explain return values. Still, it omits ordering and whether the current version is included, which are the main open questions for an edit-history endpoint.

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 `url`, `context`, `llm_model` and `conversation_id` in detail. The description's 'Requires `url`' adds nothing beyond the schema, so the baseline 3 applies.

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?

The description states a specific verb and resource: 'List every saved version of a Mastodon post.' An agent can tell this apart from mastodon_post_get (current state) and from the various *_list siblings, though it never names an alternative 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?

There is no when-to-use guidance at all: no mention of when to prefer this over mastodon_post_get, no prerequisites, no note about whether the post must be edited to return anything. The only usage statement is 'Requires `url`', which merely restates 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