PostRite

List a Discord server's channels

list_discord_channels

Read-only

List the text and announcement channels of the server a Discord bot connection is in, with whether the bot can post in each (canPost, and the reason when it cannot). A post to a bot connection needs metadata.discord.channels[platformConnectionId] set to one of these channel ids. Webhook connections post to a fixed channel and need none.

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": {
      "platformConnectionId": "<platformConnectionId>"
    },
    "name": "list_discord_channels"
  }
}

Input Schema

Name	Required	Description	Default
`organizationId`	No	Organization to act in — an id from list_organizations. Required when this connection was authorized for more than one organization; omit it when there is only one.
`platformConnectionId`	Yes	The connected account's ID (from list_platform_connections)

Output Schema

Name	Required	Description	Default
`guildId`	No
`channels`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.7/5.0

Behavior4/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 real behavioral context beyond that: the listing is filtered to text and announcement channels only, and each entry carries a canPost verdict with a reason when posting is blocked. It does not discuss pagination or channel ordering, which is the only remaining gap.

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?

Two sentences, no filler, and the core capability is front-loaded before the posting-integration guidance. Every clause carries information the agent needs.

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

Completeness5/5

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

An output schema exists, so the description need not document return values in detail, and it still names the key fields (canPost and the reason). For a read-only two-parameter tool with full schema coverage and annotations, nothing an agent needs in order to call this correctly is missing.

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?

Schema coverage is 100%, so platformConnectionId and organizationId are already documented in the schema, and the baseline would be 3. The description earns a bump by tying the connection parameter to its downstream use — the returned ids feed metadata.discord.channels[platformConnectionId] — which tells the agent why the parameter matters, not just its type.

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?

States a specific verb (list) and a precisely scoped resource (text and announcement channels of the server a Discord bot connection is in), plus the per-channel canPost flag and failure reason. An agent can distinguish it from list_platform_connections or list_pinterest_boards without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit when: the returned channel ids must be set in metadata.discord.channels[platformConnectionId] when posting to a bot connection. It also gives the when-not: webhook connections post to a fixed channel and need none of these ids, so the agent knows to skip this call in that case.

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

All PostRite tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?