mastodon-mcp-server

Directory

directory

Read-onlyIdempotent

Browse Mastodon instance profiles by recent activity or newest joins, with options to show local accounts only and set result limits.

Instructions

Browse the profile directory of the instance.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of accounts (default 20, max 80).
`local`	No	Only show local accounts (default False).
`order`	No	'active' (recently active) or 'new' (recently joined).	active

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv1.0.5Sep 12, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / limit / default
```
Added value: +20
```
addedInput schema / properties / local / default
```
Added value: +false
```
addedInput schema / properties / order / default
```
Added value: +"active"
```

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, and destructiveHint=false, so the safety profile is covered. The description adds essentially nothing beyond the name - it doesn't explain what makes a 'profile directory' distinct (e.g., only discoverable/opted-in accounts) or ordering behavior beyond what the schema already states.

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 short sentence with no waste and a clear front-loaded verb+resource. It is efficient, though the terseness contributes to the missing usage and behavioral detail.

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?

Complexity is low (three optional params, read-only), the output schema covers return values, and annotations cover safety, so the description only needs to convey purpose and routing. It does state purpose but leaves the agent without the key distinction from account_search, which is a meaningful gap for a browse tool.

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 documents limit, local, and order including the 'active'/'new' values. The description adds no parameter meaning beyond that, so the baseline 3 for full schema coverage 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 ('browse') and resource ('profile directory of the instance'), which an agent can distinguish from account_search or timeline tools. However, it does not name or contrast with those siblings, so the differentiation relies on the agent's own inference.

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 guidance on when to use this tool versus account_search, timeline_local, or trending tools. The description implies a browse-style discovery use case but offers no conditions or alternatives.

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

Deploy Server