Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_guild_integrations

Read-only

Retrieve integrations configured for a Discord server by guild ID, with optional filters for commands and role connection metadata.

Instructions

List Guild Integrations. [GET /guilds/{guild_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": {
      "guild_id": "<guild_id>"
    },
    "name": "list_guild_integrations"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID
has_commandsNohas commands
include_role_connections_metadataNoinclude role connections metadata

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/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 elsewhere. The description adds only the endpoint path, disclosing nothing about pagination, result ordering, or what an 'integration' object contains — a gap given there is no output schema.

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?

Two terse fragments, front-loaded with the tool name, but the bracketed endpoint restates context an agent rarely needs while substantive guidance is absent. Nothing is bloated, yet little of the text earns its place.

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 simple read-only list tool the annotations and schema carry most of the burden, but with no output schema the description should at least characterize the returned integrations or any pagination behavior. It says nothing beyond the endpoint.

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 description coverage is 100%, with guild_id, has_commands, and include_role_connections_metadata each documented in the schema. The description adds no meaning beyond that, so the baseline 3 applies.

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 pairs a generic verb ('List') with the resource ('Guild Integrations') and adds the REST endpoint, which confirms guild-scoped retrieval. However, it never distinguishes this from the sibling list_channel_integrations, so an agent must infer the scope difference from the name alone.

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., needing the guild ID or bot permissions), and no mention of the channel-level alternative. Usage is only implied by the name and endpoint path.

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