Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Discord announcement

discord_announcement_get
Read-onlyIdempotent

Retrieve a specific public Discord announcement by channel ID and message ID to view its content or verify a post.

Instructions

Get one public Discord announcement post by channel and message id. Requires channelId and messageId.

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

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.
messageIdYesRequired. Message id, 1 to 20 digits and at most 9223372036854775807, e.g. `267624335836053506`.
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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds only the word "public," hinting that non-public or private announcements are not retrievable, but it says nothing about error behavior for missing ids or whether the channel must match the message.

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 the action and required identifiers front-loaded; nothing is padded or redundant beyond a slight restatement of required parameters.

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 simple single-record read with full schema coverage and complete annotations, the description supplies what an agent needs to invoke it. It is slightly thin on lookup-failure behavior and the "public" restriction's consequences, but no output schema is needed to be explained.

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 channelId, messageId, context, llm_model, and conversation_id are all documented in the schema. The description merely restates that channelId and messageId are required, adding no format or constraint detail beyond the schema, which matches the baseline 3.

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?

The description gives a specific verb and resource ("Get one public Discord announcement post") and scopes it to a single item addressed by channel and message id, which implicitly separates it from the list-style siblings. It does not explicitly name an alternative, but the singular "one" is unambiguous.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer the tool applies when it already has a channel id and message id. There is no explicit when-not guidance (e.g. use the list tools when you only know the channel) and no mention of what happens if the post is missing or not public.

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