Mastodon

Get Trending

get_trending

Read-onlyIdempotent

Get currently trending posts on Mastodon. Returns popular statuses with engagement counts, authors, and trending tags.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Number of trending statuses to return (default: 10, max: 40)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes	Number of trending statuses returned
`statuses`	Yes	Trending posts

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "limit": 15
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of trending statuses returned",
+      "type": "number"
+    },
+    "statuses": {
+      "description": "Trending posts",
+      "items": {
+        "properties": {
+          "account": {
+            "description": "Author account info",
+            "properties": {
+              "acct": {
+                "description": "Full account address",
+                "type": "string"
+              },
+              "display_name": {
+                "description": "Display name",
+                "type": "string"
+              },
+              "id": {
+                "description": "Account ID",
+                "type": "string"
+              },
+              "username": {
+                "description": "Username",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "content": {
+            "description": "Post content/body",
+            "type": "string"
+          },
+          "created_at": {
+            "description": "Post creation timestamp",
+            "type": "string"
+          },
+          "favourites_count": {
+            "description": "Number of favorites",
+            "type": "number"
+          },
+          "id": {
+            "description": "Status ID",
+            "type": "string"
+          },
+          "language": {
+            "description": "Post language code",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "reblogs_count": {
+            "description": "Number of reblogs/shares",
+            "type": "number"
+          },
+          "replies_count": {
+            "description": "Number of replies",
+            "type": "number"
+          },
+          "sensitive": {
+            "description": "Content warning flag",
+            "type": "boolean"
+          },
+          "spoiler_text": {
+            "description": "Content warning text",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "tags": {
+            "description": "Hashtags in post",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "url": {
+            "description": "Status URL",
+            "type": "string"
+          },
+          "visibility": {
+            "description": "Visibility level",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "statuses"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedMay 13, 2026

removedInput schema / examples
```
Removed value: -[
-  {}
-]
```

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "coins": {
-      "description": "List of trending cryptocurrencies",
-      "items": {
-        "properties": {
-          "id": {
-            "description": "CoinGecko coin ID",
-            "type": "string"
-          },
-          "market_cap_rank": {
-            "description": "Market cap rank",
-            "type": "number"
-          },
-          "name": {
-            "description": "Coin name",
-            "type": "string"
-          },
-          "score": {
-            "description": "Trending score",
-            "type": "number"
-          },
-          "symbol": {
-            "description": "Coin symbol",
-            "type": "string"
-          }
-        },
-        "required": [
-          "id",
-          "name",
-          "symbol",
-          "market_cap_rank",
-          "score"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "coins"
-  ],
-  "type": "object"
-}New value: +null

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "coins": {
+      "description": "List of trending cryptocurrencies",
+      "items": {
+        "properties": {
+          "id": {
+            "description": "CoinGecko coin ID",
+            "type": "string"
+          },
+          "market_cap_rank": {
+            "description": "Market cap rank",
+            "type": "number"
+          },
+          "name": {
+            "description": "Coin name",
+            "type": "string"
+          },
+          "score": {
+            "description": "Trending score",
+            "type": "number"
+          },
+          "symbol": {
+            "description": "Coin symbol",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "symbol",
+          "market_cap_rank",
+          "score"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "coins"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026
- addedInput schema / examples
```
Added value: +[
+  {}
+]
```
First observedApr 22, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds context about return values (engagement counts, authors, tags) but no behavioral traits beyond annotations. No contradictions.

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?

Two concise sentences with front-loaded purpose. No redundant or irrelevant content. Every word adds value.

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?

For a simple read-only tool with one parameter and good annotations, the description is complete enough. It specifies output content, though it omits potential pagination or rate limits. Still adequate given the tool's simplicity.

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%, with the 'limit' parameter fully described (default, max). The description does not add additional semantics beyond what the schema provides, so baseline of 3 is appropriate.

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?

The description clearly states the tool retrieves trending posts from Mastodon and lists returned data (engagement counts, authors, tags). It is specific about the resource and action, but does not explicitly distinguish from siblings like 'get_timeline' or 'pipeworx_trending'.

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 tool versus alternatives. The description implies it is for trending content but does not discuss exclusions or context, leaving agents to infer usage.

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

All Mastodon tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Get Trending

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources