Fetch a single message by id.
Bulk support: accepts channel_ids, message_ids for batched execution.
| Name | Required | Description | Default |
|---|---|---|---|
| account | No | ||
| channel_id | Yes | ||
| message_id | Yes | ||
| channel_ids | No | ||
| message_ids | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare read-only, idempotent, and non-destructive. The description adds behavioral context about bulk support and the requirement for IDs, which goes beyond the annotations. No contradiction observed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two punchy sentences, front-loaded with the primary action, followed by the bulk extension. No filler or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Covers the primary function and bulk option, but lacks details on return format (especially for bulk), error handling, or account selection. With no output schema, the description still leaves some ambiguity for a complete picture.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, so the description must carry the burden. It explains the purpose of channel_ids and message_ids via 'bulk support', but leaves 'account' and the exact relationship between the arrays unclear. The required single-ID params are obvious from the name.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states it fetches a single message by ID, with an explicit verb and resource. The bulk support line further distinguishes it from list/delete/edit operations, solidifying its purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides a clear context: use this to fetch a specific message by ID, with an optional batched mode. It does not explicitly contrast with sibling tools like discord_list_messages, but the core use case is evident.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.