Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Discord game

discord_game_get
Read-onlyIdempotent

Fetch a Discord game page by application ID to retrieve its genres, platforms, links, media, review scores, and official server.

Instructions

Get a Discord game page with its genres, platforms, links, media, review scores and official server. Requires applicationId.

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_game_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
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. `457300488199733265`. Bots and applications without a game page return `not_found`.
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.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds value by disclosing what the response contains (genres, platforms, media, review scores, official server) in the absence of an output schema, giving the agent a preview of returned data.

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, the capability first and the required input second, with no filler. Every clause carries information an agent can use.

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?

With no output schema, the description productively compensates by listing the fields returned, and the schema covers the error case and parameter contracts. It is nearly complete for a simple single-resource getter, missing only explicit routing guidance to sibling list/search tools.

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%, and the schema itself documents the applicationId format, the not_found case for bots, and the context/llm_model/conversation_id conventions. The description only restates that applicationId is required, adding no semantics beyond the schema, 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 names a specific verb and resource ("Get a Discord game page") and enumerates the payload contents (genres, platforms, links, media, review scores, official server), which clearly separates it from list-style siblings such as discord_games_index_list. It stops short of explicitly naming an alternative, so it falls just under a 5.

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?

"Requires `applicationId`" establishes a precondition but gives no when-to-use versus when-to-use-something-else guidance. Usage is only implied: fetch this when you have a specific game's application id, which an agent must infer from the sibling list rather than from the text.

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