Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_embedded_activities

Read-only

Lists embedded activities for a specified Discord server by guild ID, enabling you to inspect which activities are available in that guild.

Instructions

List Embedded Activities. [GET /activities/shelf]

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_embedded_activities"
  }
}

Input Schema

NameRequiredDescriptionDefault
guild_idNoServer (guild) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/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 by structured data. The description contributes nothing beyond that—no scope, no pagination, no rate-limit or return-shape notes—so it earns no credit for added behavioral context.

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?

Two short fragments with no filler, so nothing is wasted—but the brevity is under-specification rather than efficiency. The endpoint tag is the only content beyond the name and provides little value to an agent.

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, the description should indicate what the list returns (shape, pagination, ordering), and it does not. For a listing tool with an optional filter parameter, the definition is too thin to guide correct invocation.

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?

The single parameter guild_id is fully documented in the schema (100% coverage), so the baseline of 3 applies. The description adds no meaning about whether guild_id is optional, what happens when omitted, or whether results are global versus per-server.

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?

"List Embedded Activities" simply restates the tool name, and the bracketed HTTP path adds implementation trivia rather than meaning. It does not clarify what an embedded activity is or how this differs from a sibling like launch_embedded_activity.

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 related launch tool. The agent gets no signal about when this listing is appropriate versus other list_* siblings.

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