Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_channel_integrations

Read-only

Retrieve all integrations configured for a Discord channel by channel ID. Use it to inspect connected apps, webhooks, and services before managing channel settings.

Instructions

List Channel Integrations. [GET /channels/{channel_id}/integrations]

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": {
      "channel_id": "<channel_id>"
    },
    "name": "list_channel_integrations"
  }
}

Input Schema

NameRequiredDescriptionDefault
channel_idYesChannel ID (text, voice, thread, forum or DM channel)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only the endpoint, not pagination behavior, what integrations are returned (webhooks? bots? apps?), or any auth/permission requirements tied to viewing channel integrations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very short and front-loaded, which is good, but the brevity comes at the cost of substance; the bracketed endpoint is the only content beyond the name.

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

Completeness2/5

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

For a read-only list tool with one simple param, more should be said about what an integration is and how the result is scoped. No output schema exists, so the description should at least indicate the return content, which it does not.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and channel_id is fully documented in the schema. The description adds no parameter meaning beyond the path template, so it contributes nothing over the structured field.

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

Purpose3/5

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

The description restates the tool name ('List Channel Integrations') and adds an HTTP endpoint path, but does not say what an integration is or how this differs from the sibling list_guild_integrations. It is a verb+resource, but with no scope detail beyond the URL.

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 when-to-use guidance is given. The sibling list_guild_integrations is an obvious alternative and is never mentioned, nor is any condition that would select one over the other.

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