Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_search_messages

Search messages in a Discord channel by text and optionally filter by author ID to find specific conversations or verify details.

Instructions

Search messages in a channel by text, optionally from one author.

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": {
      "channelId": "<channelId>",
      "content": "<content>"
    },
    "name": "discord_search_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
contentYesText to search for
authorIdNoDiscord id (snowflake)
channelIdYesDiscord id (snowflake)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses essentially nothing beyond the request. It does not explain result ordering, whether all messages or only recent history are searchable, the hard cap of 25 results per call and the 5000 offset ceiling, or what the response contains — all material for a search call an agent may need to page through.

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?

One tight sentence with no filler, and the resource scope is front-loaded before the qualifier. It earns its place but is thin enough that the brevity reads as under-specification rather than economy.

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 five parameters, no annotations, and no output schema, the description would need to carry pagination, permissions, and result-shape context on its own — and it does not. An agent can form the call but has no basis for planning pagination or understanding what comes back.

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 60%, and the description adds real meaning for two of the five parameters: 'by text' maps to content and 'optionally from one author' clarifies that authorId is a narrowing filter rather than a requirement. It says nothing about limit or offset, which have defaults but no schema descriptions, so those remain undocumented in both places.

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 ('Search messages in a channel') plus the primary dimension ('by text') and the optional author filter. It's clear what the tool does, but it never contrasts with discord_read_messages, which is the obvious confusable sibling for pulling channel content.

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 or when-not-to-use guidance: no statement about preferring this over discord_read_messages for keyword lookups, and no prerequisites such as the search permissions that Discord requires. The intended context is only inferable from the phrasing itself.

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