Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Mastodon server

mastodon_search_get
Read-onlyIdempotent

Search a Mastodon server for accounts, hashtags, or publicly searchable posts using a host and query. Use it to find profiles, tags, or discussions on a specific server.

Instructions

Search a Mastodon server for accounts, hashtags or posts. Requires host and query.

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>",
      "query": "<query>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "mastodon_search_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
typeNoWhat to search. Omit for accounts and hashtags. `posts` works only on servers whose software allows searching posts without a login (Pleroma, Akkoma and some others); Mastodon itself does not.
limitNoItems per page, 1 to 40. Default: 20.
queryYesRequired. Search text.
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
Behavior2/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 fully covered by structured data. The description adds nothing behavioral on top: no note on rate limits, federated/open-world variance in results, pagination, or the per-server capability differences for post search. It essentially restates the operation.

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 with the resource and scope front-loaded and no filler. The second sentence largely duplicates the schema's required array, which is minor redundancy but keeps the definition scannable.

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 7-parameter, 4-required tool with no output schema, the description is thin: it never explains the result shape, pagination via `limit`, or the unusual analytics/conversation parameters, relying entirely on the schema. Since schema coverage is complete this is workable, but the definition is only minimally sufficient for a search tool with server-dependent behavior.

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 every parameter (host, type, limit, query, context, llm_model, conversation_id) is already documented in detail. The description only repeats that host and query are required, adding no syntax, format, or constraint meaning beyond the schema. 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 (search) and resource (a Mastodon server) and enumerates what can be found: accounts, hashtags or posts. This separates it from the many single-resource siblings like mastodon_hashtag_get or mastodon_profile_get, though it does not name any 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer this is the tool for free-text discovery across a named server, and the note 'Requires `host` and `query`' sets a prerequisite. There is no when-to-use versus when-not guidance, and no mention that post search is unavailable on Mastodon proper (that caveat lives only in the schema's `type` property).

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