mastodon-mcp-server

Search

search

Read-onlyIdempotent

Find accounts, statuses, and hashtags on Mastodon. Query any Mastodon instance to retrieve matching results by category.

Instructions

Search Mastodon for accounts, statuses, and hashtags.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum results per category (default 20).
`query`	Yes	Search string.
`resolve`	No	Resolve non-local accounts/statuses (default False).
`search_type`	No	Restrict to 'accounts', 'statuses', or 'hashtags'. None returns all types.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv1.0.5Sep 12, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / limit / default
```
Added value: +20
```
addedInput schema / properties / resolve / default
```
Added value: +false
```

addedInput schema / properties / search_type / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / search_type / default
```
Added value: +null
```

changedInput schema / properties / search_type / description

Previous value: -"Restrict to 'accounts', 'statuses', or 'hashtags'."New value: +"Restrict to 'accounts', 'statuses', or 'hashtags'.\n         None returns all types."

removedInput schema / properties / search_type / type
```
Removed value: -"string"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object",
+  "x-fastmcp-wrap-result": true
+}

First observedv1.0.1Jun 26, 2026

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, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds nothing further — no note on instance-wide scope, auth requirements, rate limits, or how public/remote results are handled — leaving no value beyond structured fields.

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?

A single efficient sentence with no waste, front-loading the verb and scope. It is appropriately sized, though minimal content means it is concise almost by omission.

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?

An output schema exists, so return values need not be explained, and the annotations cover the safety profile. Still, given the overlapping account_search sibling and four parameters, the description is too thin to fully orient an agent on when this tool is the right choice.

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 all four parameters (query, limit, resolve, search_type) are documented in the schema itself. The description adds no additional parameter meaning, so the baseline of 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 (Mastodon) along with the result categories (accounts, statuses, hashtags). However, it does not distinguish itself from the sibling account_search, which overlaps on account results, so an agent cannot tell them apart from the description 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?

There is no guidance on when to use this tool versus alternatives; it never mentions the account_search sibling that overlaps its scope. No exclusions, prerequisites, or context are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server