--- name: log-discord-server-search description: "Finding a conversation in a Discord server. A log play (docs/useCases/discord/serverSearch.md): Find what someone said in a server, or a conversation the owner had there, with Discord's own search across every channel, forum post and thread at once, then read around it. This is how \"the conversation I had with about in the server\" is found in one search instead of reading a channel back hundreds of messages. This page reads and sends nothing." when_to_use: "Use when the owner asks for this, in words like: \"find the conversation I had with in about \", \"what did say in about \", \"search for \", \"read through the server and find \"" metadata: summary: "Finding a conversation in a Discord server" --- # Finding a conversation in a Discord server This is the log play `discord/serverSearch`. Before anything else, call the log MCP tool `getGuide({ useCase: "discord/serverSearch" })`: it returns this page and makes it the session's play, so every log tool's answer says which step you are on and a send with no play loaded is refused (rules 157, 158). Then follow the steps in order. Draft every message from that person's own thread and the owner's real replies (`voice` with no text, `search`), never from memory, and never send two that read alike (`sameAsSent`). Find what someone said in a server, or a conversation the owner had there, with Discord's own search across every channel, forum post and thread at once, then read around it. This is how "the conversation I had with about in the server" is found in one search instead of reading a channel back hundreds of messages. This page reads and sends nothing. How the owner asks for it: "find the conversation I had with in about ", "what did say in about ", "search for ", "read through the server and find " ## Run it from a fresh context Say: **"go on docs/useCases/discord/serverSearch.md for , looking for "**. The agent reads this page and runs the steps. ## The steps | # | Step | Tool | Done when | | --- | --- | --- | --- | | 1 | Search the server for the subject, narrowed to the person when the owner names one | `discordSearch` { account, server: "", query: "", from: "" } | hits with their time, author, text and where each one is (`" #"` or a post) | | 2 | When nothing comes back, search again with other words the owner or they would have used | `discordSearch` { account, server: "", query: "" } | the hit, or two searches with nothing | | 3 | Read the conversation around the hit, text only, in the channel or post it names | `discordRead` { account, channel: "", limit: 60, noMedia: true } | the whole exchange: what was asked and every answer | | 4 | Tell the owner what was said | the reply to the owner | who said what, when (the owner's time), quoted closely, and what it means for what the owner asked | ## What to know - **Search first, always.** Discord's search covers the whole server, including forum posts and threads; Log's own `search` only holds the mentions and replies the watcher kept from servers. Reading a channel back to look for something is the slow way. - **Search matches words.** Use the words they would have typed: "widgets", not "generative UI components". Try a second set before saying it isn't there. - **`from` narrows to one person by name.** It is matched on the hits' authors, so a short name works ("paul"). - **The answer names where each hit is.** Read it there with `discordRead`, which names the channel or post it read. - **Voice notes and images:** a hit in a voice note shows as its attachment. Read that spot without `noMedia` to have it transcribed. - What each part of a server is: the `discordServers` skill in the discord guide.