Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Steam app review summary

steam_app_reviews_summary_get
Read-onlyIdempotent

Fetch a Steam app's review totals and Steam score label by appId to gauge overall player reception.

Instructions

Get the review totals and Steam's score label for a Steam app. Requires appId.

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

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 the reviews are written in, as a Steam name or short code such as `english` or `en`, or `all`. Default: `all`.
purchaseNo`steam` is reviews by people who bought on Steam, `other` is activated keys and free copies. Default: `all`.
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 readOnly, idempotent, openWorld and non-destructive behavior, so the safety profile is covered. The description adds only the shape of the result (totals and score label) and says nothing about data recency, whether the totals respect the language/purchase filters, or any rate limits. Minimum-viable given the annotation coverage.

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?

Two short sentences with the core purpose front-loaded and no filler. The second sentence ('Requires `appId`') duplicates what the schema already marks as required, so a small amount of space is not earning its place.

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?

The tool is simple and there is no output schema, so the description bears some burden for describing return values; it names the returned content but not its structure. It also leaves open how the optional filters change the summary and which sibling to use for raw or histogram data, leaving notable gaps for an agent choosing among review 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 coverage is 100% and each parameter, including the optional `language` and `purchase` filters, is fully described in the schema. The description only repeats the `appId` requirement and adds no meaning about how those filters interact with the reported totals, 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?

States a concrete verb and resource: 'Get the review totals and Steam's score label for a Steam app.' The mention of totals and score label implicitly separates it from reviews_list (individual reviews) and reviews_histogram_get (distribution), but no sibling is named, so an agent must infer the boundary.

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?

There is no when-to-use guidance and no comparison against the many review-related siblings such as steam_app_reviews_list or steam_app_reviews_histogram_get. 'Requires `appId`' is a prerequisite, not usage guidance, and the description never says when this summary is preferable to fetching raw reviews.

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