Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Discord announcement channel

discord_announcements_list
Read-onlyIdempotent

Fetch public posts from a Discord announcement channel—including text, attachments, and reactions—by channel ID.

Instructions

List the latest public posts of a Discord announcement channel, with text, attachments and reactions. Requires channelId. Returns a list.

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "discord_announcements_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
channelIdYesRequired. Channel id, 1 to 20 digits and at most 9223372036854775807, e.g. `267631170882240512`.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds useful scope detail ('public' posts, included fields like attachments and reactions) but omits how many posts are returned, pagination, and any rate-limit or auth context.

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?

Three short sentences, front-loaded with the core action and payload, then the required param and return shape. No filler or redundant phrasing.

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 read-only list tool with a fully covered schema and a declared payload, most of what an agent needs is present. However, it omits volume/pagination behavior and does not touch on the meta-parameters (context, llm_model, conversation_id) that make up three of the four inputs.

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 100%, so all four parameters (including channelId) are documented in the schema. The description only restates 'Requires channelId' and adds no format or semantic detail beyond what the schema provides, so the 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 ('List the latest public posts of a Discord announcement channel') and enumerates the payload contents (text, attachments, reactions). It does not distinguish itself from adjacent siblings like discord_announcement_get or discord_announcements_index_list, so an agent cannot fully disambiguate from the text alone.

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 versus discord_announcement_get or discord_announcements_index_list, and no exclusions or prerequisites beyond 'Requires channelId'. The agent must infer the choice from sibling names alone.

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