Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_guild_new_member_actions

Read-only

Retrieve a Discord server's configured new-member actions by guild ID to review onboarding or automation settings.

Instructions

Get Guild New Member Actions. [GET /guilds/{guild_id}/new-member-actions]

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": "get_guild_new_member_actions"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idYesServer (guild) 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 contributes nothing beyond that — no note on whether the result is a list, whether it's paginated, whether it reflects server configuration versus member events, or what permissions scope the guild.

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 fragments with no padding and the identifier is front-loaded. It is not verbose, but that brevity comes at the cost of substance rather than from disciplined editing.

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?

With no output schema and no annotations explaining semantics, the description should say what is returned or how the data is shaped. It says nothing, leaving the agent unable to judge relevance against sibling onboarding/welcome tools.

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 coverage is 100% for the single required guild_id, and the schema already documents it as 'Server (guild) ID'. The description adds no meaning beyond the schema, so the baseline 3 applies.

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 ('Get Guild New Member Actions') and appends the HTTP route. It never explains what a 'new member action' actually is, so an agent cannot distinguish this from get_guild_new_member_welcome or get_guild_onboarding beyond guessing from the name.

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, and no mention of the neighboring new-member tools. The only inferable signal is the read verb 'Get' and the endpoint path, which is implied usage at best.

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