Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Discord servers

discord_servers_list
Read-onlyIdempotent

List public Discord servers by category, sorted by size, and paginate with a cursor to discover communities to join.

Instructions

List the public Discord server directory by category, with the largest servers first on the first page. Optional inputs: category, page and cursor. Returns a list (use cursor when paginated).

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1 to 250. Omit for the first page. The directory reorders between requests, so numbered pages can repeat servers; follow `page.nextCursor` instead.
cursorNoCursor from `page.nextCursor` of the previous response. It only works with the same filters.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
categoryNoDirectory category: `gaming`, `music`, `entertainment`, `science-tech` or `education`.
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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds genuine value with the ordering rule (largest first, first page only), but "use cursor when paginated" largely restates what the cursor parameter description already says about following page.nextCursor, and it says nothing about result size or rate limits.

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 short sentences with the core behavior front-loaded and no filler. The parenthetical about cursors is somewhat redundant with the schema but is small enough not to be wasteful.

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 read-only directory listing with a fully described schema, the definition covers purpose, ordering and pagination pointer. Since there is no output schema, a brief note on the shape of returned entries would have closed the remaining gap, but nothing required to invoke it correctly is missing.

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 six parameters, including the enum for category and the analytics/conversation plumbing, are already documented. The description only names category, page and cursor as optional inputs, adding no meaning beyond the schema; 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 public Discord server directory") plus a scope detail ("by category") and ordering behavior ("largest servers first on the first page"). It is clear what the tool does, but it does not name the nearby alternatives (discord_servers_search, discord_servers_index_list), so an agent must infer the distinction from names alone.

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 implied by the description: browse the directory by category, use cursor when paginated. There is no explicit when-to-use or when-not-to-use guidance and no mention of the sibling search or index_list tools, so routing between them is left to inference.

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