Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Mastodon posts by id

mastodon_posts_batch_get
Read-onlyIdempotent

Fetch up to 20 Mastodon posts by ID from a specified server in one request, returning a list for batch retrieval and analysis.

Instructions

Get up to 20 Mastodon posts by their ids. Requires host and ids. 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": {
      "host": "<host>",
      "ids": "<ids>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "mastodon_posts_batch_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesRequired. Comma-separated post ids on `host`, 1 to 20. Ids belong to that server.
hostYesRequired. The Mastodon server to ask, e.g. `mastodon.social`. A server URL is also accepted. The server you name is the one that answers.
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

B3.2/5.0
Behavior3/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 and idempotency profile is fully covered by structured data. The description adds little beyond that — the 20-id cap is meaningful, but nothing is said about what happens when an id is missing or invalid, whether cross-server ids are rejected, or what the returned list items contain.

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 front-loaded sentences with the operation and its limit stated first. The middle sentence ('Requires `host` and `ids`') is wasted on information the schema already marks as required, which is the only real redundancy.

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?

There is no output schema, so the brief 'Returns a list' is the only signal about return shape and it does not describe the post objects an agent would receive. With five parameters, four of them required, including meta-parameters like context, llm_model and conversation_id, the description is adequate only because the schema documents each one thoroughly.

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 parameters carry rich descriptions including the host/ids relationship, the id pattern, the analytics-only nature of llm_model, and the conversation_id echo rule. The description merely restates that host and ids are required, 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?

States a specific verb and resource (get Mastodon posts) plus a concrete scope bound (up to 20, by id), which implicitly separates it from the single-post sibling mastodon_post_get. It stops short of naming any alternative explicitly, so an agent must infer the batch-vs-single distinction from the wording alone.

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?

The description gives no when-to-use guidance at all: nothing about when to prefer this over mastodon_post_get for a single id, over mastodon_profile_posts_list for timeline-style retrieval, or over mastodon_search_get. There are no exclusions or prerequisites beyond the schema's required-field list, leaving the agent to infer usage from the tool name.

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