Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

modify_guild_sticker

Update a Discord server sticker's name, description, or tags by providing the guild and sticker IDs.

Instructions

Edit a sticker's name, description or tags. [PATCH /guilds/{guild_id}/stickers/{sticker_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": {
      "guild_id": "<guild_id>",
      "sticker_id": "<sticker_id>"
    },
    "name": "modify_guild_sticker"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName
tagsNoTags / related emoji name
reasonNoReason (shown in the audit log)
guild_idYesServer (guild) ID
sticker_idYesSticker ID
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is provided. The description adds the HTTP method and the fact that only name/description/tags are editable, but it does not state the permission requirements, whether unspecified fields are left untouched (partial PATCH semantics), or that a 'reason' can be surfaced in the audit log.

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, front-loaded with the action and field list, with the endpoint path as compact supporting detail. No filler, though the PATCH path duplicates information an agent can infer from the name and provides little operational value.

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 simple field-update tool with high schema coverage and safety annotations, this is adequate - an agent can call it correctly. It stops short of complete because permission requirements, partial-update behavior, and the distinction from other sticker-mutation tools are unstated, and no output schema exists to show what the PATCH returns.

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 83%, so the schema already documents all six parameters, including that 'reason' appears in the audit log. The description merely restates the three editable fields and adds nothing about formats, validation rules, or how guild_id/sticker_id identify the target. Baseline 3 applies because the schema carries the load.

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 gives a specific verb ('Edit') plus resource ('a sticker') and enumerates the mutable fields (name, description, tags), which cleanly separates it from create_guild_sticker, delete_guild_sticker and get_guild_sticker. The bracketed PATCH path reinforces that this is a mutation on a single existing sticker.

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 explicit statement of when to use this versus the sibling sticker tools - no mention that deletion belongs to delete_guild_sticker, that reading belongs to get_guild_sticker, or that creation belongs to create_guild_sticker. The only guidance is implicit in the endpoint path, that this is guild-scoped rather than pack- or global-scoped.

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