Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_user_profile

Read-only

Retrieve a Discord user's full profile, including bio, pronouns, badges, connected accounts, mutual servers and friends. Use it to inspect identity and shared connections.

Instructions

Get a user's full profile: bio, pronouns, badges, connected accounts, mutual servers and friends. [GET /users/{user_id}/profile]

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": {
      "user_id": "<user_id>"
    },
    "name": "get_user_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesUser ID
guild_idNoInclude this server's member profile
with_mutual_guildsNowith mutual guilds
with_mutual_friendsNowith mutual friends
with_mutual_friends_countNowith mutual friends count

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 the endpoint and the profile contents, but it does not disclose auth requirements, rate limits, or other behavioral constraints; with annotations present, this is adequate but not rich.

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?

The description is a single front-loaded sentence that names the action and enumerates the key profile contents, followed by a brief endpoint tag. There is no wasteful prose, and the structure makes the core purpose immediately scannable.

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 read-only retrieval tool with five mostly optional parameters, the description identifies the returned profile contents and the annotations cover safety, while the schema documents parameters. The main remaining gap is that the optional mutual and guild_id flags are not explained in practical terms, but the definition is largely complete.

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 the five parameters are already documented in the input schema, and the baseline is 3. The description loosely maps 'mutual servers and friends' to the optional mutual flags, but it does not explain their exact effect or the guild_id member-profile scoping beyond what the schema provides.

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 uses a specific verb ('Get') and resource ('user's full profile') and lists the profile components, so an agent knows this returns richer data than a basic user object. It stops short of explicitly distinguishing this from siblings such as get_user or get_guild_profile, so it is clear but not maximally differentiable.

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

Usage Guidelines3/5

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

Usage is implied by the phrase 'full profile' and the listed fields; an agent can infer it should call this when profile details are needed. However, there is no explicit when-to-use guidance, no when-not-to-use condition, and no named alternative such as get_user for basic user data.

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