Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_set_banner

Set or clear a Discord account banner by providing an image HTTPS URL or data URI; pass an empty string to remove the current banner.

Instructions

Set the account banner from an image URL or data URI. Empty string clears it.

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": {
      "url": "<url>"
    },
    "name": "discord_set_banner"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYeshttps URL, data: URI, or empty string to clear

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It discloses that this is a mutation, the accepted input encodings, and the non-obvious clearing semantics via empty string, which is real added value, but it omits permission requirements, any size/format limits, and failure behavior for an invalid URL.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with zero waste: the primary action and its input forms come first, and the less obvious clearing behavior follows. Nothing redundant or buried.

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 one-parameter mutation tool with no output schema and no annotations, the definition covers the action, accepted input forms, and the clear path. The remaining gap is operational context (auth/permission needs, invalid-input handling), which is minor for a tool this simple.

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 100% and the single parameter's schema description ('https URL, data: URI, or empty string to clear') already says everything the description says about 'url'. The description adds no format or constraint detail beyond that, so baseline 3 applies.

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 ('Set the account banner') and names the accepted input forms plus the clear operation. It is clearly distinct from the neighbouring discord_set_avatar and discord_set_accent_color tools by resource name, though it never explicitly contrasts with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes the usage condition concrete: supply an image URL or data URI to set, or an empty string to clear. That covers the main branching decision an agent must make, but says nothing about when this tool is preferable or preconditions such as authentication.

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