Skip to main content
Glama
cameronrye

AT Protocol MCP Server

list_conversations

Read-only

List your Bluesky direct-message conversations, returning each conversation's ID, members, unread count, mute state, status, and last message. Requires authentication.

Instructions

List the authenticated user's Bluesky direct-message conversations (chat.bsky.convo.listConvos, proxied to the bsky.chat service). Returns each conversation's id, members, unread count, mute state, status (request/accepted) and a last-message preview, plus a pagination cursor. Requires authentication with an app password created with "Allow access to your direct messages" enabled. Use get_conversation_messages to read a conversation and send_direct_message to reply. Subject to per-tool rate limiting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax conversations per page (1-100, default 50).
cursorNoOpaque pagination cursor from the previous response cursor field; omit for the first page.
statusNoFilter by conversation status: 'request' = incoming chat requests not yet accepted; 'accepted' = active conversations. Omit to list both.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successYesWhether the request succeeded.
conversationsYesThe conversations for this page, most recently active first.
cursorNoOpaque cursor for the next page; absent when there are no more results.
hasMoreYesWhether another page is available (a cursor was returned).
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, indicating safe, read-only operation. The description adds context about authentication requirements (app password with DMs allowed) and mentions per-tool rate limiting, which goes beyond annotations. No contradictions.

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?

The description is concise, front-loaded with the main action, and contains only essential information. Every sentence adds value, covering purpose, API, contents, auth, and related tools.

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?

Given the presence of an output schema, the description does not need to explain return values. It covers authentication, pagination (cursor), and points to related tools. The tool is simple and the description is complete for its complexity.

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 100%, so the baseline is 3. The description does not add significant meaning beyond what the schema provides for each parameter. The schema already documents limit, cursor, and status adequately.

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 clearly states it lists the authenticated user's direct-message conversations, specifying the underlying API and what each conversation includes (id, members, unread count, etc.). It distinguishes from sibling tools like get_conversation_messages and send_direct_message.

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 provides explicit guidance on when to use this tool (list conversations) and directs the agent to get_conversation_messages for reading and send_direct_message for replying. It also mentions the authentication requirement. However, it does not explicitly state when not to use it.

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