Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

download_attachments

Downloads a Discord message's attachments or a direct CDN URL to local files and returns the saved file paths.

Instructions

Download a message's attachments (or any CDN URL) to local files and return their paths.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "download_attachments"
  }
}

Input Schema

NameRequiredDescriptionDefault
dirNoFolder (default /root/.discord-mcp/downloads)
urlNoOr a direct attachment/CDN URL
messageNoMessage link, or message ID with channel_id
channel_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false; the description usefully confirms the local-file write and that it returns paths. It does not disclose overwrite behavior, filename collisions, multiple-attachment handling, or size/network limits, which matter given the open-world hint.

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?

A single well-formed sentence that front-loads the action and packs the two input modes plus the return value with no filler.

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

Completeness3/5

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

For a 4-parameter, zero-required tool with no output schema, stating that paths are returned is helpful, but the description leaves ambiguous what happens when a message has many attachments, where names come from, and how message/channel_id combine.

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?

With 75% schema coverage the baseline is 3, and the description goes beyond it by framing 'message' and 'url' as two alternative input modes ('or any CDN URL') and by implying 'dir' is the local destination. Only the pairing of message ID with channel_id remains unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Download a message's attachments ... to local files') and additionally covers the direct-URL mode. It is clearly distinguishable from the sibling set, which contains no other download tool, though it never explicitly contrasts itself with anything.

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

Usage Guidelines3/5

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

Implicit usage guidance: use it to fetch a message's attachments, or a raw CDN URL, into local storage. There is no statement of when not to use it, no prerequisites (e.g. needing channel_id alongside a message ID), and no named alternative.

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

Deploy Server

Other Tools