Skip to main content
Glama
Sign In

Bluesky

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Followers

get_followers
Read-onlyIdempotent

Get a user's followers on Bluesky by handle. Returns follower profiles including handles, display names, bios, and follower counts.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "handle": "alice.bsky.social"
    },
    "name": "get_followers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of followers (1-100, default 50)
handleYesBluesky handle

Output Schema

NameRequiredDescriptionDefault
followersYesList of follower profiles

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "followers": {
+      "description": "List of follower profiles",
+      "items": {
+        "properties": {
+          "description": {
+            "description": "Follower's bio",
+            "type": "string"
+          },
+          "did": {
+            "description": "Decentralized identifier",
+            "type": "string"
+          },
+          "displayName": {
+            "description": "Follower's display name",
+            "type": "string"
+          },
+          "followers": {
+            "description": "Follower's follower count",
+            "type": "number"
+          },
+          "following": {
+            "description": "Follower's following count",
+            "type": "number"
+          },
+          "handle": {
+            "description": "Follower's handle",
+            "type": "string"
+          },
+          "posts": {
+            "description": "Follower's post count",
+            "type": "number"
+          }
+        },
+        "required": [
+          "did",
+          "handle",
+          "displayName",
+          "description",
+          "followers",
+          "following",
+          "posts"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "followers"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "handle": "alice.bsky.social"
+  },
+  {
+    "handle": "jack.bsky.social",
+    "limit": 100
+  }
+]
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already convey read-only, open-world, idempotent, and non-destructive behavior. The description adds that follower profiles are returned, but does not mention pagination, rate limits, or other nuances. It does not contradict annotations.

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 two short sentences: the first states the core action, the second summarizes the return value. No unnecessary words or redundancy.

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 2-param tool with strong annotations and an output schema, the description is sufficient. It could mention pagination or ordering, but those are not critical for basic use and the schema/annotations already cover safety and parameters.

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 coverage is 100%: both handle and limit have clear descriptions. The description simply notes 'by handle,' which aligns with the schema but adds no new semantic detail beyond the structured parameter definitions.

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 uses a specific verb and resource: 'Get a user's followers on Bluesky by handle.' It also enumerates the returned fields (handles, display names, bios, follower counts), making the tool's purpose clear and distinguishing it from siblings like get_follows.

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?

The description does not explicitly state when to use this tool versus alternatives such as get_follows. Usage is implied by the name and phrasing, but no when-not or alternative guidance is provided.

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

All Bluesky toolsInspect
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.

Resources