mastodon-mcp-server

Trending Links

trending_links

Read-onlyIdempotent

Fetch trending links (articles) from any Mastodon instance; set a limit to control the number of returned results.

Instructions

Get trending links (articles) on the instance.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of links (default 10).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.0.5Sep 12, 2026

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

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

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=true, so safety is covered. The description adds that results are scoped to the instance, a useful behavioral detail, but nothing about freshness window, pagination, or ordering.

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 zero waste. Nothing to trim and nothing buried.

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?

Output schema exists, so return format needn't be explained. Annotations cover safety. The description is sufficient for this simple, single-parameter read tool, though a note on ranking or time window would fully close the loop.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one optional parameter (limit) with 100% schema coverage including its default. The description adds no parameter detail but the schema fully covers it; per rules, zero required params with full coverage warrants a 4.

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?

Clear verb+resource: 'Get trending links (articles) on the instance.' Distinguishes from siblings trending_tags and trending_statuses by specifying 'links (articles)'. Slight overlap with trending_statuses, but the parenthetical clarifies the resource.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Trending' implies a discovery/context use case, but there is no explicit when-to-use or when-not-to-use guidance versus trending_tags or trending_statuses. Implied usage only.

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

Deploy Server