Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_premium_guild_subscriptions

Read-only

Retrieve premium subscriptions for a Discord server using its guild ID, optionally including ended subscriptions.

Instructions

List Premium Guild Subscriptions. [GET /guilds/{guild_id}/premium/subscriptions]

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_premium_guild_subscriptions"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) ID
include_endedNoinclude ended

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.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, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only the underlying REST endpoint, and says nothing about required permissions (premium subscription listing typically needs elevated guild permissions), pagination, or result ordering.

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?

Two short, front-loaded items with zero filler: the operation name followed by the endpoint. Nothing is wasted, though the endpoint tagline occupies space that could have carried a usage note.

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 two-parameter read-only listing tool with full schema coverage and annotations, the description is minimally sufficient — an agent knows what it fetches and with what required id. However, with no output schema, the description could have said what a subscription record contains, and it omits the permission and pagination context.

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%, so both guild_id and include_ended are documented in the schema; baseline is 3. The description adds no extra meaning, and the terse schema wording 'include ended' is not elaborated on in the description.

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 gives a specific verb and resource ('List Premium Guild Subscriptions') and the bracketed endpoint reinforces the resource scope. It is clear enough to separate from siblings such as list_guild_members or list_guild_roles, though it offers no explicit sibling differentiation beyond the resource noun.

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 guidance on when to call this versus related guild-listing tools, nor any prerequisite or exclusion. Nothing indicates when include_ended should be used, which is the main decision an agent faces here.

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