Skip to main content
Glama

Channel details (admin)

discord_admin_get_channel
Read-only

Retrieve full details for a Discord channel or category, including type, topic, slowmode, forum tags, and every permission override showing who is allowed or denied what.

Instructions

Everything about one channel or category: type, category, topic or guidelines, slowmode, forum tags and settings, and every permission override spelled out (who is allowed or denied what).

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": "discord_admin_get_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
channel_idYesChannel, forum, category or thread ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description usefully adds that permission overrides are fully expanded ('who is allowed or denied what'), signalling a large, nested payload, but says nothing about access requirements, failure modes for inaccessible channels, or payload size.

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

Conciseness4/5

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

One sentence, front-loaded with scope ('Everything about one channel or category'), and every listed field earns its place by telling the agent what comes back. Slightly list-heavy but free of filler.

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?

With no output schema, the description carries the return-value burden and does so by enumerating the fields returned, which is the key missing piece for this tool. It remains silent on error behavior and whether the response can be very large, which are the only meaningful gaps for a one-parameter read.

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% with a single required parameter, so baseline is 3. The description reinforces the accepted resource types (channel or category) but adds no format or edge-case detail beyond the schema's own 'Channel, forum, category or thread ID' note.

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 the resource (one channel or category) and enumerates the exact payload: type, category, topic/guidelines, slowmode, forum tags, and permission overrides. That enumeration makes clear this is a full-detail read, distinguishable from edit/delete/create siblings without opening a schema. It stops short of explicitly contrasting itself with a lighter-weight list or the server-level getter.

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?

There is no when-to-use guidance, no prerequisites (e.g. that the bot needs admin scope or that the ID must belong to the calling guild), and no mention of alternatives such as discord_admin_get_server or discord_admin_edit_channel. The read-only nature is only implied by the framing 'Everything about...'.

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