Skip to main content
Glama

Post a thread

create_thread
Destructive

Post multiple Bluesky posts as one thread, each replying to the previous. Validates every part before publishing, preventing partial threads; requires confirmation because it goes public instantly.

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.
confirmNoMust be true for this to run. The result is public immediately or cannot be undone, so it is refused without an explicit confirmation.
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.
Install Server

TDQS

A4.6/5.0
Behavior5/5

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

Even though annotations already mark this as destructive, the description adds substantial behavioral detail: all parts are validated against the 300-character limit before anything publishes, so the thread never half-publishes; media/quote/reply controls only affect the first post; and the result is public immediately, requiring confirm: true. This goes well beyond the annotations and schema.

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 sentences with no filler. The core action is stated first, followed by atomicity, first-post scoping, and the confirmation requirement—each sentence earns its place and important behavior is front-loaded.

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 complex 9-parameter destructive tool with no output schema, the description covers the key invocation-critical behaviors: thread chaining, pre-publication validation, first-post scoping, public visibility, and mandatory confirmation. It does not mention return values, but that is not essential for safe invocation.

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 schema already documents most parameters. The description adds meaningful semantics by explaining that the posts list forms a reply chain, that media/quote/reply controls apply only to the first post, and that length validation is all-or-nothing. This supplements rather than merely repeats the schema.

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 names a specific verb ('Publish') and resource ('several posts as one thread'), and distinguishes it from the single-post sibling create_post by describing the chained-reply structure. This makes the tool's purpose immediately identifiable.

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?

The description clearly implies this tool is for multi-post threads and states that media, quotes, and reply controls apply to the first post. It does not explicitly name create_post as the alternative for single posts, but the context is clear enough for an agent to choose correctly.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/navidmoazzez/bluesky-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server