Skip to main content
Glama
thenavidm

bluesky-mcp

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Post to Bluesky

create_post
Destructive

Publish a Bluesky post with text, up to four images, video, link cards, quotes, or replies. Auto-links URLs, hashtags, and mentions; requires confirm: true to post publicly.

Instructions

Publish a post. Handles plain text, up to four images with alt text, a video, a link card, a quote, and replies. URLs, #hashtags and @mentions in the text are turned into real links automatically. You do not need to format them. The limit is 300 characters; for anything longer use create_thread. Public the moment it runs, so it needs confirm: true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linkNoA link preview card.
tagsNoExtra hashtags that should apply without appearing in the text.
textYesThe post body. Up to 300 characters, counted the way Bluesky counts them.
langsNoBCP-47 language codes for the post text. Defaults to ['en'].
quoteNoThe post to quote, as an at:// URI or a bsky.app link.
imagesNoUp to four images.
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_toNoThe post being replied to, as an at:// URI or a bsky.app link.
video_altNoAlt text for the video.
video_urlNoPublic URL of an MP4. Uploaded through Bluesky's transcoder, which takes a few seconds.
allow_quotesNoSet false to stop anyone quoting 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

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and non-idempotency, so the safety profile is partly covered. The description adds genuinely non-structured context: the post goes public the instant it runs (hence confirm), and URLs/hashtags/mentions are auto-linked without manual formatting. It does not discuss failure/reversibility, but the added behavioral notes are substantive.

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?

Roughly five compact sentences, all front-loaded: purpose first, capabilities next, then the character limit + sibling alternative, then the confirm gate. No filler or repetition of schema text.

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 13-parameter mutation with 100% schema coverage and no output schema, the description covers what an agent needs to invoke it safely: scope, media capabilities, length ceiling, sibling alternative, and the confirm requirement. Only failure modes and the resulting post identifier are left unaddressed, which is minor.

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 description coverage is 100%, so every parameter is already documented and the baseline is 3. The description reinforces the 300-character limit and auto-linking but adds little parameter detail beyond what the nested schema already carries (alt text, media constraints, reply_control semantics, account selection).

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 and resource ("Publish a post") and enumerates the content shapes it supports (text, images+alt, video, link card, quote, replies), so an agent can immediately match it to a publishing intent. It also names create_thread as the boundary case for longer content, distinguishing it from the nearest sibling.

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?

Gives an explicit alternative with its selecting condition (over 300 characters → create_thread) and states the precondition that the action is public immediately and therefore requires confirm: true. It doesn't cover other adjacent cases (editing, deleting, scheduling), but the core routing guidance is clear.

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