Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_server_insights

Read-only

Retrieves Discord Server Insights analytics reports for community growth, joins, leavers, retention, engagement, channel stats, and audience data.

Instructions

Server Insights analytics (Community servers, needs View Server Insights): growth, joins, leavers, retention, engagement, channel stats, audience.

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>",
      "report": "<report>"
    },
    "name": "get_server_insights"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoISO8601 end
startNoISO8601 start
reportYes
guild_idYes
intervalNo1 day, 2 week, 3 month

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered without description help. The description adds the permission and Community-server scoping constraints, which is genuine added context. It does not cover anything about how reports are returned, whether data is aggregated over the start/end window, or how the interval affects bucketing.

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?

A single dense sentence that front-loads the resource name and puts the critical prerequisite in parentheses before the content list. Nothing is redundant. It is compressed to the point of being telegraphic, but no sentence is wasted.

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 tool with a 25-value required enum, a date range, and an interval parameter, the description covers the permission gate but leaves report semantics and interval behavior unexplained, and there is no output schema to fall back on. An agent can invoke it, but choosing the right report and interval requires reading the raw enum strings.

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 60%: start and end have ISO8601 descriptions, interval has a cryptic '1 day, 2 week, 3 month' note, guild_id is undocumented, and the 25-value report enum has no per-value explanation. The description's category list (growth, joins, leavers, retention, engagement, channel stats, audience) loosely maps onto the enum prefixes but omits channel-following and welcome-screen, so it only partially compensates. Baseline 3 is the right level.

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 names the specific resource (Server Insights analytics) and enumerates the analytic families it covers: growth, joins, leavers, retention, engagement, channel stats, audience. That is enough to distinguish it from the neighboring get_* tools, which cover channels, users, emoji, and audit logs. It stops short of stating a verb like 'retrieve' or 'report on', but the intent is unambiguous.

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?

The parenthetical '(Community servers, needs View Server Insights)' gives a real precondition: the guild must be a Community server and the caller needs the View Server Insights permission. That is useful gating information. However, there is no explicit guidance on when to pick this over other analytics-adjacent tools, and nothing about what happens when the precondition is not met.

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