discord-mcp-server

get_embed_analytics

Retrieve analytics data for a specific Discord embed message to track performance metrics and engagement insights.

Instructions

Obtenir les analytics d'un embed spécifique

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": {
      "embedId": "<embedId>"
    },
    "name": "get_embed_analytics"
  }
}

Input Schema

Name	Required	Description	Default
`embedId`	Yes	ID du message embed

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 9, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states the action ('Obtenir les analytics') without disclosing behavioral traits such as permissions needed, rate limits, response format, or whether it's a safe read operation. This leaves significant gaps in understanding how the tool behaves.

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?

The description is a single, efficient sentence in French that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, though it could benefit from more detail to improve clarity.

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?

Given the tool has no annotations, no output schema, and a simple input schema, the description is incomplete. It lacks details on what 'analytics' entails, the return format, or any behavioral context, making it insufficient for an agent to fully understand the tool's operation.

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%, with the parameter 'embedId' clearly documented in the schema. The description adds no additional meaning beyond implying it's for a 'specific embed,' which is already covered by the schema. Baseline score of 3 is appropriate as the schema handles the parameter documentation adequately.

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

Purpose3/5

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

The description states the purpose as 'Obtenir les analytics d'un embed spécifique' (Get analytics for a specific embed), which clearly indicates a read operation targeting analytics data. However, it doesn't differentiate from sibling tools like 'get_embed_details' or 'list_embeds' that might also retrieve embed-related information, making it somewhat vague about its specific scope.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, context, or exclusions, leaving the agent to infer usage based on the name alone without explicit direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server