Skip to main content
Glama
thenavidm

bluesky-mcp

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Post a thread

create_thread
Destructive

Publish multiple posts as one Bluesky thread, each replying to the last. Checks every part against the 300-character limit before posting, preventing half-published threads.

Instructions

Publish several posts as one thread, each replying to the last. Every part is checked against the 300-character limit before anything is posted, so a thread never half-publishes because part four was too long. Media, quotes and reply controls apply to the first post. Public the moment it runs, so it needs confirm: true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linkNoA link card on the first post.
langsNo
postsYesThe parts, in order. Each up to 300 characters.
quoteNoA post quoted by the first post.
imagesNoImages on the first post.
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.
confirmNoSet true only when the user asked for exactly this action.
reply_toNoStart the thread as a reply to this post.
reply_controlNoWho can reply. 'following' means accounts you follow; 'followers' means accounts that follow you; 'mentioned' means only accounts named in the post.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.0.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true for this to run. The result is public immediately or cannot be undone, so it is refused without an explicit confirmation."New value: +"Set true only when the user asked for exactly this action."
    • removedInput schema / properties / images / items / additionalProperties
      Removed value: -false
    • removedInput schema / properties / link / additionalProperties
      Removed value: -false
  2. First observedv1.1.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, openWorldHint=true and idempotentHint=false, so the safety bar is partly met. The description adds real context annotations cannot convey: all parts are validated against the 300-char limit before anything posts (no half-published threads), and media/quote/reply controls attach only to the first post. It does not describe rate limits or the return shape.

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?

Four tight sentences, front-loaded with the core action, then atomicity guarantee, then attachment scoping, then the confirm gate. No filler, and each sentence carries distinct information.

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 9-param mutation with nested objects and no output schema, the description covers the high-risk behaviors (atomic validation, first-post-only attachments, confirm gate). It omits the return value/thread identifier and does not restate the account default, leaving a small gap an agent might notice.

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 89%, so the baseline is 3. The description earns above baseline by clarifying scope that the schema leaves ambiguous: 'Media, quotes and reply controls apply to the first post' tells the agent that quote, images and reply_control are not per-part, which no parameter description states.

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?

States a specific verb+resource: 'Publish several posts as one thread, each replying to the last.' The multi-post/threaded nature clearly separates it from a single-post sibling like create_post, though it never names that sibling explicitly.

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?

Usage is implied rather than stated: the confirm:true requirement and the atomicity note hint at when this is appropriate, but the description never says 'use this instead of create_post when you have multiple parts' or sets any preconditions beyond confirm.

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