mastodon-mcp-server

Account Search

account_search

Read-onlyIdempotent

Search Mastodon accounts by username or display name to locate profiles and find the right people to follow or mention.

Instructions

Search for accounts by username or display name.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of results (default 10, max 80).
`query`	Yes	Search string (username or display name).
`resolve`	No	Whether to resolve non-local accounts (default False).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.0.5Sep 12, 2026

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

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

B3.1/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully covered without the description. The description adds nothing behavioral on top: it doesn't note that non-local accounts require resolve, that results are capped, or anything about rate limits.

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 the resource and matching fields front-loaded and no waste. It is appropriately sized, though it could carry a bit more routing information without becoming bloated.

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 simple read-only search with full schema coverage, rich annotations, and an existing output schema, the essentials are covered. The only gap is sibling disambiguation, which is minor given the structured data available.

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 limit, query, and resolve are all documented in the schema; the description only echoes the query semantics ('username or display name'). Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Search for accounts') plus the match fields (username or display name). It is reasonably distinct from account_get or account_verify, but it never differentiates itself from the broader sibling 'search' tool, so it falls short of a 5.

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 explicit when-to-use guidance, no mention of alternatives like account_get, directory, or the generic 'search' tool, and no exclusions. The agent must infer the use case from the one-line purpose.

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

Deploy Server