bluesky-mcp-server

Search Bluesky Actors

bsky_search_actors

Read-onlyIdempotent

Find Bluesky accounts by name or handle fragment. Returns ranked profiles with handle, DID, displayName, bio, pronouns when the account set them, and Bluesky verification status — which tells a verified account from a look-alike handle. Follower, following, and post counts and the website are not on this view — bsky_get_profile returns them for one account. Use before bsky_get_profile or bsky_get_author_feed when you have a name but not a confirmed handle. Supports cursor-based pagination for browsing beyond the first page of results.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of actors to return (1–100). Default 25.
`query`	Yes	Name or handle fragment to search for, e.g. "alice" or "nytimes.com". Must not be blank.
`cursor`	No	Opaque pagination cursor from a previous response to the same query. Omit for the first page.

Output Schema

TableJSON Schema

Name	Required	Description
`cap`	No	The limit applied to this page.
`error`	No	Present when the call failed. Absent on success.
`shown`	No	Number of actors returned on this page.
`actors`	No	Matching actor profiles, ranked by relevance.
`cursor`	No	Opaque cursor for the next page — pass it back with the same query. Absent on the last page.
`notice`	No	Guidance when the result set is empty or constrained.
`truncated`	No	True when Bluesky returned a cursor for another page, whatever this page held — pages often hold fewer actors than limit and still continue.
`totalReturned`	No	Number of actors in this response page.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 25, 2026

addedOutput schema / properties / actors / items / properties / verification

Added value: +{
+  "additionalProperties": false,
+  "description": "Bluesky verification of this account — what tells it from a look-alike handle. Absent when Bluesky sent none. Who issued it is on bsky_get_profile.",
+  "properties": {
+    "trustedVerifierStatus": {
+      "description": "Whether this account is itself a trusted verifier — same values as verifiedStatus.",
+      "type": "string"
+    },
+    "verifiedStatus": {
+      "description": "Whether a trusted verifier verified this account: \"valid\", \"invalid\" (verified once, no longer holds), or \"none\". Passed through as Bluesky sends it, so another value may appear.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "verifiedStatus",
+    "trustedVerifierStatus"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedSep 25, 2026

changedOutput schema / properties / error / properties / data / properties / reason / description

Previous value: -"Machine-readable failure mode."New value: +"Machine-readable failure mode. Declared by this tool: `invalid_cursor`: Bluesky could not continue from the cursor the request carried — it answers a cursor it cannot decode with HTTP 400. Other values are possible when a failure originates below the handler."

addedOutput schema / properties / error / properties / data / properties / reason / examples
```
Added value: +[
+  "invalid_cursor"
+]
```

Changed4 schema fields changedSep 25, 2026

changedInput schema / properties / cursor / description

Previous value: -"Opaque pagination cursor from a previous response. Note: the public Bluesky AppView restricts cursor-based search pagination for unauthenticated requests — passing a cursor may return a 403 error. Cursor pagination is reliable only for bsky_get_author_feed and bsky_get_follows."New value: +"Opaque pagination cursor from a previous response to the same query. Omit for the first page."

removedOutput schema / properties / actors / items / properties / followersCount

Removed value: -{
-  "description": "Number of followers.",
-  "type": "number"
-}

changedOutput schema / properties / cursor / description

Previous value: -"Opaque cursor returned by the API. Unreliable for unauthenticated search requests on the public AppView — passing it on a subsequent call may return a 403 error."New value: +"Opaque cursor for the next page — pass it back with the same query. Absent on the last page."

changedOutput schema / properties / truncated / description

Previous value: -"True when more actors match than were returned on this page."New value: +"True when Bluesky returned a cursor for another page, whatever this page held — pages often hold fewer actors than limit and still continue."

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": [
+      "actors",
+      "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: -[
-  "actors",
-  "totalReturned"
-]

Changed1 schema field changedJul 31, 2026

addedOutput schema / properties / actors / items / properties / pronouns

Added value: +{
+  "description": "Free-form pronouns the account set, e.g. \"they/he\". Absent when it set none. Account-authored text bounded only by length, not a fixed vocabulary — read it as written rather than parsing it.",
+  "type": "string"
+}

Changed3 schema fields changedJul 31, 2026

changedInput schema / properties / query / description

Previous value: -"Name or handle fragment to search for, e.g. \"alice\" or \"nytimes.com\"."New value: +"Name or handle fragment to search for, e.g. \"alice\" or \"nytimes.com\". Must not be blank."

addedInput schema / properties / query / minLength
```
Added value: +1
```
addedInput schema / properties / query / pattern
```
Added value: +"\\S"
```

Changed3 schema fields changedJun 16, 2026

addedOutput schema / properties / cap

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

addedOutput schema / properties / shown

Added value: +{
+  "description": "Number of actors returned on this page.",
+  "type": "number"
+}

addedOutput schema / properties / truncated

Added value: +{
+  "description": "True when more actors match than were returned on this page.",
+  "type": "boolean"
+}

First observedJun 7, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnly, openWorld, and idempotent hints. The description adds valuable behavioral context: it lists exact fields returned, explains the verification status nuance (look-alike detection), and notes what is absent. It also clarifies pagination support. No contradiction with annotations, and it enriches the agent's understanding of what to expect.

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 front-loaded with the core purpose, then adds essential details about returned fields, exclusions, and usage context. Every sentence earns its place; no fluff. It's compact but thorough, and the sibling routing is woven in naturally.

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?

Given the presence of an output schema (which covers return values), the description covers all necessary guidance: what it does, what it doesn't do, when to use it, and pagination. For a search tool with three well-documented parameters and safe annotations, this is complete. No critical information is missing.

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?

Schema coverage is 100% and each parameter has a description. The description adds marginal value by explaining the 'ranked' nature of results and explicitly mentioning cursor-based pagination for browsing beyond the first page, which reinforces the cursor's purpose. It doesn't redefine params but adds usage context that schema lacks.

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 description starts with 'Find Bluesky accounts by name or handle fragment,' a specific verb and resource. It distinguishes itself from siblings by explicitly listing what is not returned (follower/following/post counts, website) and pointing to bsky_get_profile for those. This makes the tool's scope unambiguous.

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?

It gives direct, actionable guidance: 'Use before bsky_get_profile or bsky_get_author_feed when you have a name but not a confirmed handle.' It also tells the agent what this tool is NOT for (detailed stats) and which sibling to use instead. No inference required.

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.