Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

launch_embedded_activity

Launches a Discord Activity (game or app) in a voice channel you are currently in, using channel, application, and session IDs.

Instructions

Launch an Activity (game/app) in a voice channel you are in. [POST /activities/{channel_id}/{application_id}]

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": {
      "channel_id": "<channel_id>",
      "application_id": "<application_id>",
      "session_id": "<session_id>"
    },
    "name": "launch_embedded_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
channel_idYesChannel ID (text, voice, thread, forum or DM channel)
session_idYessession id
application_idYesApplication (app/bot) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world call, so the safety profile is covered structurally. The description adds one genuinely useful prerequisite — the caller must be present in the target voice channel — but says nothing about required permissions, what happens if an activity is already running, or whether the launch can be undone.

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 sentences with the action stated first and the constraint immediately after — well front-loaded with no filler prose. The bracketed HTTP route is developer-facing noise that does not help an agent select or invoke the tool.

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 three-parameter, fully schematized mutation with annotations covering the safety profile and no output schema, the definition supplies the action, the resource, and the key precondition. Remaining gaps — permissions and re-launch behavior — are secondary for this complexity level.

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 all three parameters are documented structurally and the baseline is 3. The description adds only the constraint that channel_id must be a voice channel the caller occupies; it adds no meaning for session_id or application_id beyond the schema.

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?

States a specific verb and resource ("Launch an Activity (game/app)") and disambiguates what an Activity is, which the bare name does not. It does not distinguish itself from siblings such as set_activity or set_headless_activity, so an agent cannot tell launch from set by this definition alone.

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 phrase "in a voice channel you are in" implies a precondition for use, giving an implicit context signal. There is no explicit when-to-use versus when-not, and no named alternative such as set_headless_activity or clear_activity for other cases.

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