mastodon-mcp-server

Timeline Hashtag

timeline_hashtag

Read-onlyIdempotent

Retrieve Mastodon statuses by hashtag to monitor discussions and discover relevant content.

Instructions

Get statuses with a specific hashtag.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of statuses (default 20, max 40).
`local`	No	Only show statuses from the local instance (default False).
`hashtag`	Yes	Hashtag to search (without the # prefix).

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 / local / 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 readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is fully covered. The description adds nothing beyond that – no pagination behavior, no note on rate limits, no return-shape hints – it essentially restates the name.

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 wasted words. It is efficient, though its brevity edges toward under-specification rather than true conciseness.

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 annotations cover safety. Still, for a timeline query tool with pagination-relevant parameters (limit), the absence of any usage or paging context leaves it only minimally complete.

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%, including the 'without the # prefix' guidance, limit max of 40, and local-instance toggle, so baseline is 3. The description contributes no additional parameter meaning beyond what the schema already documents.

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') plus the scoping qualifier ('with a specific hashtag'), which separates it from timeline_home/local/public. It doesn't explicitly name those siblings, 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?

No when-to-use guidance and no mention of alternatives such as search, trending_tags, or the other timeline_* tools. The agent must infer the selection context from the name alone.

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

Deploy Server