Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get several Steam apps

steam_apps_batch_get
Read-onlyIdempotent

Fetch up to 100 Steam apps in one call as compact or full records. Retrieve app details, pricing, and metadata for multiple Steam app IDs at once.

Instructions

Get up to 100 Steam apps in one call, as short records or full ones. Requires ids.

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

Input Schema

NameRequiredDescriptionDefault
idsYesRequired. Steam app ids, comma-separated, 1 to 100, e.g. `570,730,620`. Duplicates are dropped.
fieldsNo`compact` (default) returns the fields lists use. `full` adds a short description, franchises, platforms, category ids, tags, languages, trailers, screenshots, purchase options and images.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
countryNoCountry the prices are shown for, as an ISO 3166-1 alpha-2 code. Default: `US`. An app not sold in this country returns `lookupStatus` `not_found` with `unavailableInCountry` true.
languageNoLanguage of the text: a Steam language name or short code such as `german` or `de`. Default: `en`.
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.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description's only added behavioral detail is the 100-item cap and the short-vs-full record choice, both of which are already expressible from the schema (maxItems: 100, fields enum). It says nothing about how missing or country-unavailable ids come back (lookupStatus/not_found, which only appears in the country parameter text) or about partial results.

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, front-loaded with the action and scope, no restating of the title and no filler. Every clause carries information an agent can act on.

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?

For a 7-parameter batch tool with no output schema, the description is thin: it omits the return envelope (how per-id results or lookupStatus failures are shaped) and the fact that the meaningful optional knobs are country/language/fields. The rich schema compensates for most parameter gaps, but an agent reading only the description would not know the shape of what comes back.

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 documents ids limits, duplicate dropping, fields, country, language, llm_model and conversation_id. The description only restates that `ids` is required and caps at 100, adding no format hints or edge-case meaning beyond the structured fields; 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 ("Get up to 100 Steam apps in one call") plus the output-shape choice (short vs full records), which is enough to tell it apart from single-app tools. It stops short of naming the sibling it replaces (e.g. steam_app_get or steam_apps_search), so sibling differentiation is implied by the batch/limit wording rather than stated.

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?

"Requires `ids`" is a parameter constraint, not usage guidance. The description never says when to prefer this over a single-app fetch or a search/browse tool, nor does it mention prerequisites such as already having app ids in hand or the conversation_id sequencing caveat that lives only in the schema.

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