Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Steam app reviews

steam_app_reviews_list
Read-onlyIdempotent

Fetch Steam app user reviews filtered by language, sentiment, playtime, and date to analyze player feedback or research opinions. Use the app ID and paginate with a cursor.

Instructions

List the user reviews of a Steam app, filtered by language, sentiment, playtime and date. Requires appId. 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": {
      "appId": "<appId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "steam_app_reviews_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOnly reviews written on or before this date (UTC). Must be on or after `from`.
daysNoWith `sort=helpful`: how many days back to rank, 1 to 365. Default: 365.
fromNoOnly reviews written on or after this date (UTC). Must be on or before `to`.
sortNo`recent` is newest first and reaches the first review; `updated` is by last edit; `helpful` is Steam's helpfulness ranking and only looks at the last `days` days. Default: `recent`.
appIdYesRequired. Steam app id, the number in the store URL, e.g. `570` for Dota 2. A store app URL is also accepted.
limitNoReviews per page, 1 to 100. Default: 20.
cursorNoPass `page.nextCursor` from the previous response, with the same filters, to get the next page.
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.
sentimentNoOnly reviews that recommend (`positive`) or don't recommend (`negative`) the app. Default: `all`.
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.
maxPlaytimeHoursNoOnly reviews by players with at most this many hours in the app. Must be at least `minPlaytimeHours`.
minPlaytimeHoursNoOnly reviews by players with at least this many hours in the app. Must not exceed `maxPlaytimeHours`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds that results are returned as a list and should use a cursor when paginated, which is useful behavioral context, but it does not describe rate limits, auth behavior, freshness, or result ordering beyond what the schema provides.

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?

The description is two tightly written sentences with the primary purpose front-loaded. Every clause earns its place by covering purpose, filters, required input, return type, and pagination in a compact form.

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?

Given a 15-parameter tool with 100% schema description coverage and no output schema, the description covers the essential behavior: it lists reviews, supports filtering, requires appId, and uses a cursor for pagination. It omits some complexity around sort/helpful-window behavior and meta parameters, but those are fully documented in the schema.

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 parameters, enums, defaults, and constraints are already documented in the input schema. The description summarizes the filter categories and notes that appId is required, but adds little meaning beyond the schema text.

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 states a specific verb and resource: list user reviews of a Steam app, with named filters for language, sentiment, playtime, and date. It is clear what the tool does, but it does not explicitly distinguish this list operation from sibling tools such as steam_app_reviews_summary_get or steam_app_reviews_histogram_get.

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?

The description gives a pagination instruction via cursor, but it does not explain when to use this tool instead of the summary or histogram siblings, nor does it state any when-not conditions. The use case is implied by the name, but the definition provides no explicit routing guidance.

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