Skip to main content
Glama
cameronrye

AT Protocol MCP Server

send_direct_message

Send a plain-text direct message on Bluesky to an existing conversation or to a recipient by handle/DID, automatically resolving or creating the conversation.

Instructions

Send a plain-text Bluesky direct message (chat.bsky.convo.sendMessage, proxied to the bsky.chat service). Target either an existing conversation by convoId, or a recipient by handle/DID via member — the conversation is then resolved (or created) automatically with chat.bsky.convo.getConvoForMembers. Message text is limited to 1000 graphemes / 10000 UTF-8 bytes and is sent without facets (mentions/links appear as plain text). Requires authentication with an app password created with "Allow access to your direct messages" enabled; the recipient's settings must also allow DMs from you. Subject to per-tool rate limiting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
convoIdNoId of an existing conversation to send into (from list_conversations). Provide exactly one of convoId or member.
memberNoHandle (e.g. bob.bsky.social) or DID of the account to message. The conversation is resolved (or created) via chat.bsky.convo.getConvoForMembers, so no prior conversation is needed. Provide exactly one of convoId or member.
textYesPlain-text message body (max 1000 graphemes / 10000 UTF-8 bytes). Mentions, links and hashtags are sent as plain text — no facets are attached.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successYesWhether the message was sent.
messageYesHuman-readable status message.
convoIdYesId of the conversation the message was sent into; reuse it for follow-up messages to skip conversation resolution.
recipientDidNoDID the member parameter resolved to. Present only when member was used to target the message.
sentMessageYesThe message as recorded by the chat service.
Behavior5/5

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

Adds significant behavioral details beyond annotations: message limits (1000 graphemes/10000 bytes), no facets, rate limiting, and authentication requirements. No contradiction with annotations.

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 sentences covering purpose, usage, and constraints with no fluff. Information is well-structured and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Handles all aspects: purpose, parameters, requirements, limitations, and rate limiting. Output schema exists, so return value explanation not needed.

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 covers all parameters with descriptions (100% coverage). Description adds extra context like max limits and plain-text behavior, which is valuable beyond 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?

Clear verb ('Send') and resource ('Bluesky direct message'), with specific details about protocol and service. Distinguishes from sibling tools like list_conversations or get_conversation_messages.

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?

Explains when to use convoId vs member, and mentions authentication and recipient requirements. Lacks explicit when-not-to-use or alternatives, but context is clear.

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

Install Server

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/cameronrye/atproto-mcp'

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