Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Discord server index

discord_servers_index_list
Read-onlyIdempotent

Retrieve Discord server IDs and slugs from the public directory, using optional page and cursor inputs to collect server identifiers for lookup or analysis.

Instructions

List Discord server ids and slugs from the public directory. Optional inputs: 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_index_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1 to 200. Each page returns up to 500 ids and slugs; omit for the first page and pass `page.nextCursor` to continue.
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.
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 declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds useful context that the data comes from a public directory and that results are paginated with a cursor, but says nothing about result volume limits beyond the schema, rate limits, or auth requirements.

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 purpose and followed by inputs and return shape. The cursor sentence is slightly redundant against the schema but is short 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?

There is no output schema, and the description does state what comes back (a list of ids and slugs) and how to continue pagination. For a simple read-only index tool with fully documented parameters, that is close to sufficient; it only lacks sibling disambiguation.

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 the schema already fully documents page, cursor, context, llm_model and conversation_id. The description merely restates that page and cursor are optional and that cursor is for pagination, adding no meaning beyond the structured fields, 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?

The description gives a specific verb and resource ("List Discord server ids and slugs") plus a scope ("from the public directory"), which is clearly narrower than a full server listing. It does not explicitly contrast with siblings like discord_servers_list or discord_servers_search, so the agent must infer that this is the lightweight index variant.

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 offered is "use cursor when paginated," which is a parameter-usage note rather than when-to-use guidance. Nothing states when an agent should pick this tool over discord_servers_list, discord_servers_search, or discord_server_get, nor any prerequisite conditions.

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