Bluesky MCP Server

get-dm-messages

Retrieve direct messages from a specific Bluesky conversation by providing its ID. Fetch up to 100 messages with a configurable limit.

Instructions

Get messages from a specific DM conversation on Bluesky

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "convoId": "<convoId>"
    },
    "name": "get-dm-messages"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Number of messages to fetch
`convoId`	Yes	The conversation ID (get from get-conversations)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

B3.4/5.0

Behavior2/5

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

The description states only that it retrieves messages from a specific DM conversation, adding little beyond the tool name. With no annotations, it does not disclose pagination, ordering, authentication requirements, error behavior, or that this is a read-only operation, though 'get' implies a read.

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?

Single sentence, front-loaded with the verb, no filler. It conveys the core purpose in eight words and earns its place.

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 simple 2-parameter read tool with no output schema, the description is mostly sufficient: it names the action and target. However, without annotations or an output schema, it leaves unspecified return format and ordering, which would be useful. Overall it is adequate but not exhaustive.

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?

The description itself adds no parameter information, but the input schema covers 100% of parameters with clear descriptions: convoId identifies the conversation (and references get-conversations) and limit controls fetch count. Therefore the schema carries the semantic weight, giving the baseline score.

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 uses the specific verb 'Get' paired with the resource 'messages from a specific DM conversation' and scopes it to Bluesky, clearly distinguishing it from sibling tools like get-conversations (lists conversations) and send-dm (sends messages).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use or alternative guidance is provided in the description. The only usage hint ('get from get-conversations') lives in the parameter schema, not the tool description, so an agent selecting this tool gets no context about prerequisites or when to prefer it.

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