bluesky-mcp-server

Get Bluesky Trending Topics

bsky_get_trending

Read-only

Fetch the current real-time trending topics on Bluesky. Returns topics with display name, Bluesky's one-sentence summary of the story, post count, category (politics, sports, pop-culture, etc.), status, start time, and the representative accounts driving each topic — so "who is talking about this" needs no follow-up call. Entry point for "what is Bluesky talking about right now". Each trend is a feed: pass its feedUri to bsky_get_feed to read the trend's posts. Note: uses the app.bsky.unspecced.getTrends endpoint, which is not part of Bluesky's stable lexicon and may change without notice.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of trending topics to return (1–25). Default 10. 25 is Bluesky's maximum.

Output Schema

TableJSON Schema

Name	Required	Description
`cap`	No	The limit applied to this request.
`error`	No	Present when the call failed. Absent on success.
`shown`	No	Number of trending topics returned.
`notice`	No	Guidance when the result set is empty or constrained.
`trends`	No	Current trending topics, ordered by prominence.
`truncated`	No	True when more topics were trending than limit — raising limit shows them. Never set at limit 25, Bluesky's maximum.
`totalReturned`	No	Number of trending topics returned.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedSep 25, 2026

changedInput schema / properties / limit / description

Previous value: -"Maximum number of trending topics to return (1–25). Default 10."New value: +"Maximum number of trending topics to return (1–25). Default 10. 25 is Bluesky's maximum."

addedOutput schema / properties / trends / items / properties / description

Added value: +{
+  "description": "Bluesky's one-sentence summary of the story behind the trend. Third-party text, rendered quoted.",
+  "type": "string"
+}

addedOutput schema / properties / trends / items / properties / feedUri

Added value: +{
+  "description": "AT-URI of the feed that collects this trend's posts — pass it to bsky_get_feed as-is to read them. Parsed from link; absent when link is missing or is not a feed page.",
+  "type": "string"
+}

changedOutput schema / properties / trends / items / properties / link / description

Previous value: -"Full URL associated with this trending topic (e.g. https://bsky.app/…), if provided."New value: +"The trend feed's page on bsky.app (https://bsky.app/profile/…/feed/…), if provided."

changedOutput schema / properties / trends / items / properties / status / description

Previous value: -"Velocity signal, e.g. \"hot\" or \"rising\"."New value: +"Velocity signal as Bluesky reports it, e.g. \"hot\", \"cooling\", or \"stale\"."

changedOutput schema / properties / trends / items / properties / topic / description

Previous value: -"Opaque topic slug, e.g. \"ailaunch2025\". Use as a search term in bsky_search_posts."New value: +"Record key of the feed generator behind this trend, e.g. \"1d558a3bc9ff\" — an identifier, not a search term. Read the trend's posts through feedUri."

changedOutput schema / properties / truncated / description

Previous value: -"True when the topic list was capped at the requested limit; more may exist."New value: +"True when more topics were trending than limit — raising limit shows them. Never set at limit 25, Bluesky's maximum."

Changed6 schema fields changedAug 25, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "trends",
+      "totalReturned"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode.",
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "trends",
-  "totalReturned"
-]

Changed1 schema field changedJul 31, 2026

addedOutput schema / properties / trends / items / properties / actors

Added value: +{
+  "description": "Representative accounts posting about this topic — the AppView returns five per trend. Pass a handle to bsky_get_author_feed or bsky_get_profile instead of searching for authors.",
+  "items": {
+    "additionalProperties": false,
+    "description": "A representative account posting about this topic.",
+    "properties": {
+      "did": {
+        "description": "Permanent DID of the actor.",
+        "type": "string"
+      },
+      "displayName": {
+        "description": "Display name set by the actor.",
+        "type": "string"
+      },
+      "handle": {
+        "description": "Human-readable handle, e.g. \"alice.bsky.social\".",
+        "type": "string"
+      }
+    },
+    "required": [
+      "did",
+      "handle"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Changed4 schema fields changedJun 16, 2026

addedOutput schema / properties / cap

Added value: +{
+  "description": "The limit applied to this request.",
+  "type": "number"
+}

addedOutput schema / properties / notice

Added value: +{
+  "description": "Guidance when the result set is empty or constrained.",
+  "type": "string"
+}

addedOutput schema / properties / shown

Added value: +{
+  "description": "Number of trending topics returned.",
+  "type": "number"
+}

addedOutput schema / properties / truncated

Added value: +{
+  "description": "True when the topic list was capped at the requested limit; more may exist.",
+  "type": "boolean"
+}

First observedJun 7, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The annotations already communicate read-only and open-world characteristics, and the description adds value by noting that the underlying endpoint is not part of Bluesky's stable lexicon and may change without notice. It also discloses that the response already includes representative accounts, so the agent knows no follow-up is needed for that information.

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?

The description is three focused sentences: one establishes the core purpose and result, one covers the comparison question and follow-up call, and one covers the stability caveat. Every sentence earns its place, and there is no filler or repeated schema content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter, read-only tool with an output schema and sibling routing already described, the description is complete. It tells the agent when to call it, what it returns, how to continue to bsky_get_feed, and why the endpoint behavior may be risky. Nothing essential is missing.

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?

The only parameter, limit, is already fully described in the schema with default, minimum, maximum, and even the note that 25 is Bluesky's maximum. The description does not add parameter-specific meaning, but with 100% schema coverage the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence identifies a specific verb and resource: 'Fetch the current real-time trending topics on Bluesky.' It also positions the tool as the entry point for discovering what Bluesky is discussing, and clarifies that each trend is a feed that can be consumed via bsky_get_feed, preventing confusion with sibling tools.

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

Usage Guidelines5/5

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

The description explicitly tells the agent when to use the tool, using the phrase 'Entry point for what is Bluesky talking about right now.' It also routes follow-up behavior to bsky_get_feed by instructing the agent to pass the trend's feedUri, which is clear guidance on how this tool connects to its siblings.

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

All bluesky-mcp-server 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.