Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_user_connection_subreddits

Read-only

Lists the subreddits associated with a user's Reddit connection ID so you can inspect which communities are linked to that connected account.

Instructions

List User Connection Subreddits. [GET /users/@me/connections/reddit/{connection_id}/subreddits]

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": {
      "connection_id": "<connection_id>"
    },
    "name": "list_user_connection_subreddits"
  }
}

Input Schema

NameRequiredDescriptionDefault
connection_idYesConnection account ID

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 nothing beyond them: no indication of pagination, result limits, OAuth scope requirements, or what happens when the connection is not a Reddit account. For an open-world remote read, that context is what would have earned credit.

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?

Extremely short with no filler, but the length comes from under-specification rather than efficiency; the first clause merely repeats the tool name. It is front-loaded and parseable, though the bracketed route is the only substantive content.

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?

For a simple single-parameter read tool with full schema coverage and complete read-only annotations, an agent has enough to invoke it correctly. Missing details are secondary: platform scoping is only implied by the URL, and nothing describes the returned list or its paging.

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?

Only one parameter exists and it is fully documented in the schema as 'Connection account ID' (100% coverage), so the baseline applies. The description does not clarify how to obtain that connection_id or whether it is the Discord-side connection identifier, adding no meaning beyond the schema.

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

Purpose2/5

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

The description restates the tool name verbatim ('List User Connection Subreddits') and appends the raw HTTP route. The endpoint path does hint that this is Reddit-specific and scoped to a connection, but no verb-and-resource explanation goes beyond the name, and it does nothing to separate this from siblings like list_user_connections or list_user_linked_connections.

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 prerequisite (e.g. that a Reddit connection must exist and be authorized), and no pointer to an alternative tool for other platforms or for the connections themselves. The agent must infer the use case from the name alone.

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