Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bluesky_followers

Fetch a paginated list of a Bluesky account's followers by handle or DID, with limit and cursor for continuing pages. Returns profile details for each follower.

Instructions

A Bluesky account's followers. Returns a page of a Bluesky account's followers. actor is required and is a handle such as bsky.app or a DID. limit is 1 to 100 (default 25); pass the returned cursor back to continue. Each follower has did, handle, display_name, description, avatar_url and created_at, and subject describes the account itself.

Input Schema

NameRequiredDescriptionDefault
actorYesA handle (e.g. bsky.app) or DID
limitNoPage size, 1-100
cursorNoPagination cursor from a previous response's cursor field

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does reasonably well: it discloses the paginated nature, the cursor continuation mechanism, the default page size, and the exact fields returned per follower. It stops short of mentioning auth requirements or rate limits, but for a read-only list operation the behavioral picture is largely complete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence 'A Bluesky account's followers.' is mildly redundant with the following sentence, but the rest is dense, front-loaded, and every clause (params, pagination, return fields) earns its place.

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?

With no annotations and no output schema, the description must cover behavior and returns, and it does: parameters, defaults, pagination, and the follower object shape are all present. The main omission is any distinction from the closely related bluesky_follows sibling.

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%, so the baseline is 3, but the description adds real value beyond the schema: it supplies the default limit of 25 (absent from the schema) and clarifies the cursor round-trip and the handle/DID format for actor.

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 states a specific verb and resource: 'Returns a page of a Bluesky account's followers.' An agent can immediately understand the operation. However, it never distinguishes itself from the sibling bluesky_follows (accounts the actor follows), which is the one confusion risk for this tool.

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?

There is no guidance on when to use this tool versus alternatives such as bluesky_follows, bluesky_profile, or bluesky_search_actors. The only usage-like sentence ('pass the returned cursor back to continue') is really pagination mechanics, not tool-selection guidance.

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

Deploy Server

Other Tools