Skip to main content
Glama
thenavidm

bluesky-mcp

by thenavidm

Search accounts

search_actors
Read-onlyIdempotent

Find Bluesky accounts by name, handle, or bio text without credentials. Get bios and follower counts to distinguish real profiles from impersonators.

Instructions

Find Bluesky accounts by name, handle or bio text. Works without credentials. Returns each account's bio and follower counts, so you can tell the real one from the impersonators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesName, handle or keyword.
limitNoHow many. Default 25.
cursorNo
accountNoWhich connected account to act as, by handle (for example 'alice.bsky.social' or just 'alice'). Defaults to the first connected account. Call list_accounts to see them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds two things annotations cannot: the no-credential auth requirement and the shape of what comes back (bio, follower counts). Pagination behavior via cursor is left unstated.

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?

Three short sentences, no filler, with the core capability front-loaded and the practical payoff (spotting impersonators) last. Every sentence 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 output schema, the description usefully discloses the return fields, and it covers the credential requirement. It omits pagination semantics for cursor, which is the only meaningful gap for a search tool of this size.

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 75% and the q parameter is already documented as "Name, handle or keyword". The description adds only marginal value by naming "bio text" as a searchable surface; limit, cursor and account are untouched. Baseline 3 is appropriate.

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?

States a specific verb (Find) and resource (Bluesky accounts) plus the searchable fields (name, handle, bio text). Clearly separable from siblings like search_posts, search_feeds and get_profile without opening any schema.

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

Usage Guidelines4/5

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

"Works without credentials" gives a concrete precondition an agent can act on, and the impersonator use case implies the intended scenario. However, it never names alternatives (e.g. get_profile for a known handle) or states when not to use this search.

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