Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_search

Read-onlyIdempotent

Search Discord guild messages by content, author, or channel to locate specific conversations and references quickly.

Instructions

Search messages in a Discord guild.

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>"
    },
    "name": "discord_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentNo
guild_idYes
author_idNo
bot_tokenNoBot token. Optional when connected in UnClick or the documented env var is set.
channel_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.11
    • addedInput schema / properties / bot_token / description
      Added value: +"Bot token. Optional when connected in UnClick or the documented env var is set."
    • changedInput schema / required
      Previous value: -[
-  "bot_token",
-  "guild_id"
-]New value: +[
+  "guild_id"
+]
  2. Addedv0.1.5

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so safety is covered. The description adds nothing else: no mention of pagination/result limits, whether at least one filter is required, rate limiting, or Discord search API constraints (e.g., guild-level search may require specific permissions).

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?

A single short sentence, so it is front-loaded and free of waste, but the brevity is under-specification rather than effective concision. There is room to add necessary filter and scope detail.

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, 5 parameters at low coverage, and no annotation gaps filled, the description leaves the agent without enough to call the tool correctly — e.g., whether content/author_id/channel_id are filters and how results are returned or bounded.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 20% (only bot_token is documented), so the description must compensate but does not. It says nothing about content, author_id, or channel_id semantics, nor whether these act as filters or whether one is mandatory in practice.

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: searching messages within a Discord guild scope. However it provides no differentiation from siblings like discord_read or discord_thread, leaving the agent to infer that this is a keyword/filter-based retrieval rather than a sequential read.

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 on when to use this over discord_read, discord_thread, or discord_channels, and no indication of prerequisites (bot token, permissions, required filters). The agent must guess between sibling message-retrieval tools.

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