mastodon-mcp-server

Account Statuses

account_statuses

Read-onlyIdempotent

Fetch statuses for a specific Mastodon account by numeric ID. Filter by media, replies, or reblogs and limit results.

Instructions

Get statuses posted by a specific account.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of results (default 20, max 40).
`account_id`	Yes	Numeric account ID.
`only_media`	No	Only return statuses with media (default False).
`exclude_reblogs`	No	Exclude reblogs (default False).
`exclude_replies`	No	Exclude replies (default False).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv1.0.5Sep 12, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / exclude_reblogs / default
```
Added value: +false
```
- addedInput schema / properties / exclude_replies / default
```
Added value: +false
```
- addedInput schema / properties / limit / default
```
Added value: +20
```
- addedInput schema / properties / only_media / 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

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: no mention of visibility constraints, rate limiting, or pagination behavior for a tool whose default limit of 20 is capped at 40.

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, front-loaded sentence with no filler. It is appropriately terse for a simple read tool, though it is arguably too terse to earn a top score given the sibling ambiguity it leaves unaddressed.

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 and rich annotations cover the safety profile, so the description need not explain return values. Still, it omits result ordering, pagination, and any hint of how it differs from timeline tools, leaving a modest gap for a 5-parameter account-scoped list operation.

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 (limit, account_id, only_media, exclude_reblogs, exclude_replies) is already documented in the schema. The description adds no extra 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 and resource ('Get statuses posted by a specific account'), which is clear enough to act on. However, it does not differentiate itself from overlapping siblings such as timeline_home, timeline_hashtag, or search, all of which also return statuses.

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?

No guidance on when to use this versus the timeline_* or search siblings, no prerequisites, and no mention of whether the account must be public or followed. The agent must infer the context entirely.

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

Deploy Server