Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List similar Discord applications

discord_application_similar_list
Read-onlyIdempotent

List applications that Discord's app directory marks as similar to a given application, with paged results and cursor support for continuing through additional matches.

Instructions

List the applications Discord's app directory shows as similar to one application, paged. Requires applicationId. 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": {
      "applicationId": "<applicationId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "discord_application_similar_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1 to 25. Omit for the first page; use the previous response's `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.
applicationIdYesRequired. Application id, 1 to 20 digits and at most 9223372036854775807, e.g. `936929561302675456`.
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, open-world and non-destructive, so safety is covered by the structured data. The description adds that results are paged and that the cursor continues the same query, which is genuine but modest context. It does not describe ordering, result size, or what an empty result means.

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 scope, with no filler. 'Requires `applicationId`' mildly duplicates the schema's required list, keeping it just short of ideal.

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 paged list with full schema coverage and no output schema, the definition covers the essential call pattern and pagination habit. It leaves the shape and ordering of the returned list implicit, but the annotations and schema carry most of the remaining burden.

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 coverage is 100%, so every parameter is already documented in the schema, including the applicationId pattern and the cursor/page semantics. The description only restates requiredness of applicationId and cursor continuation, adding nothing the schema does not already say; 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?

Names a specific verb and resource: list the applications the Discord app directory shows as similar to one application, and adds the paging scope. It is clear what the tool returns, but it never distinguishes itself from siblings such as discord_application_get or the index/collection list tools.

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?

The prerequisite ('Requires `applicationId`') and the cursor-following habit ('use cursor when paginated') are useful usage cues. However, it gives no when-to-use guidance or exclusions relative to the application lookup and other list tools, so the agent must infer the intended moment from the name 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