Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Mastodon post

mastodon_post_get
Read-onlyIdempotent

Fetch a public Mastodon post by URL to retrieve its text, media, polls, link card, engagement counts, and author details for content analysis or verification.

Instructions

Get a public Mastodon post by its URL: text, media, polls, link card, counts and author. Requires url.

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_get"
  }
}

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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description still adds real behavioral value beyond them: the word "public" signals a visibility restriction (private/direct posts are out of scope), and the field enumeration compensates for the missing output schema. It stops short of explaining remote-instance or failure behavior.

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?

One front-loaded sentence covering purpose, key, and payload — no wasted prose. The trailing "Requires `url`" slightly duplicates the schema's required list, a small redundancy in an otherwise tight definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-record read tool with full annotation coverage and no output schema, the description supplies what an agent needs: the lookup key and the returned fields. Residual gaps (behavior on deleted/private posts, remote server rate limits) are minor rather than blocking.

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% and the schema itself explains the subtle point that the URL's server is the server queried because post ids are server-scoped. The description only restates "Requires `url`," adding no meaning 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 gives a specific verb and resource ("Get a public Mastodon post") and states the lookup key ("by its URL"), then enumerates what comes back: text, media, polls, link card, counts, author. That is enough to separate it from platform siblings like bluesky_post_get or reddit_post_get, but it never distinguishes it from Mastodon-specific siblings such as mastodon_posts_batch_get or mastodon_post_context_get.

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: you call it when you have a post URL. There is no explicit when-to-use / when-not-to-use guidance, no pointer to mastodon_posts_batch_get for multiple posts or mastodon_post_context_get for thread/reply context, and no note that non-public or deleted posts will fail.

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