Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Steam app achievements

steam_app_achievements_list
Read-onlyIdempotent

Retrieve a Steam app's achievements and the share of players who earned each to assess completion difficulty or popularity.

Instructions

List a Steam app's achievements with the share of players who earned each. Requires appId. Returns a list.

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

Input Schema

NameRequiredDescriptionDefault
appIdYesRequired. Steam app id, the number in the store URL, e.g. `570` for Dota 2. A store app URL is also accepted.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
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

A3.5/5.0
Behavior3/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 only that results include global achievement completion percentages; it says nothing about pagination, rate limits, empty results for apps without achievements, or errors for invalid appIds.

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 with the core purpose front-loaded and no filler. The closing 'Returns a list' is near-tautological and could have carried more information, but it costs almost nothing.

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 simple read-only list tool with fully documented parameters and no output schema, the description covers what the tool does and the shape of the data (achievements plus earn percentages). Only the per-item fields and pagination/absence behavior are left unstated, which is a minor gap.

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 five parameters including context, llm_model, language and conversation_id are documented in the schema itself. The description repeats only the appId requirement and adds no meaning about the language parameter's effect on achievement names or the conversation_id handshake.

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 a Steam app's achievements) and adds the distinguishing content of the payload — the share of players who earned each achievement. That separates it from siblings like steam_app_news_list or steam_app_reviews_list without needing to name them.

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 'Requires `appId`' note gives a precondition, but there is no explicit when-to-use guidance and no mention of alternatives such as steam_app_get or steam_apps_batch_get for multi-app lookups. Usage is implied by the tool name rather than stated.

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