mastodon-mcp-server

Timeline Public

timeline_public

Read-onlyIdempotent

To view public posts across the fediverse, retrieve the federated public timeline from Mastodon, with options to limit results and filter for remote statuses.

Instructions

Get the federated public timeline.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of statuses (default 20, max 40).
`remote`	No	Only show remote statuses (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: +20
```
addedInput schema / properties / remote / 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, openWorldHint, and non-destructive behavior, so safety is covered. The description adds only the content scope ('federated public') and says nothing about pagination, authentication requirements, or rate limits. It adds marginal value beyond the 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler. For a two-parameter read tool, this is appropriately sized and every word earns its place.

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?

The output schema covers return values and annotations cover the safety profile, so the description need not explain those. However, for a paginated federated feed, the description omits any mention of pagination behavior or auth requirements, leaving it just barely adequate.

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 and remote are already fully documented with defaults and max values. The description adds no parameter information, which is acceptable but unhelpful; 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 and resource ('Get the ... timeline') and the qualifier 'federated public' distinguishes it from timeline_home, timeline_local, and timeline_hashtag without naming them. The scope is identifiable, though it relies on the reader's understanding of Mastodon-style timelines to differentiate siblings.

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 when-to-use guidance, no prerequisites, and no alternatives named. An agent must infer from the word 'federated' that this is the cross-instance public feed rather than timeline_local. Implied at best, and the calibration for a no-guidance description is 2.

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

Deploy Server