Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Discord server

discord_server_get
Read-onlyIdempotent

Fetches a Discord server's public page by server ID, returning members, categories, keywords, links, and announcements for community research and verification.

Instructions

Get a Discord server's public page with its members, categories, keywords, links and announcements. Requires serverId.

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": {
      "serverId": "<serverId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "discord_server_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
includeNo`widget` adds the public guild widget summary. Default: none.
serverIdYesRequired. Server id, 17 to 20 digits and at most 9223372036854775807, e.g. `267624335836053506`. A server with no public page or subscription store page returns `not_found`.
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.
announcementsNoInclude the announcement channels for this server. Default: true.
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.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds that this is a *public* page view, which usefully implies the not_found outcome for servers without a public page, but it says nothing about cost, rate limits, or that a conversation_id handshake gates parallel calls.

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?

Two sentences, front-loaded with the resource and its returned fields, nothing wasted. The trailing "Requires `serverId`" is surplus given the required array, a minor deduction.

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?

With no output schema, the description is the only place the payload shape appears, and it gives a partial field list, omitting details on how the optional widget and announcement data alter the response. Six parameters with three required are fully documented in the schema, so the remaining gap is modest but real.

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

Parameters5/5

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

Schema description coverage is 100%, so the baseline is 3; here each parameter carries real operational meaning in the schema itself, including the exact serverId digit constraints, the not_found failure mode, the widget enum, and the explicit instruction not to invent a conversation_id or guess a model identifier. The description's "Requires `serverId`" is the one redundant element, which does not pull the score down from the baseline-plus level.

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?

Names a specific verb and resource ("Get a Discord server's public page") and enumerates what the page surfaces: members, categories, keywords, links, announcements. That is well beyond a tautology, though it never distinguishes itself from the nearby discord_server_widget_get or the list/search siblings.

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?

The only guidance is the prerequisite "Requires `serverId`," which the schema already enforces via required/pattern. There is no statement of when to reach for this tool versus discord_servers_search, discord_servers_list, or discord_server_widget_get, and no note that the `include: widget` option partly duplicates the widget sibling.

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