Skip to main content
Glama
icue

Steam Review and Forum MCP

by icue
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_steam_review_corpus

Create a public Steam review corpus in the background and get a corpus_id for status checks, local queries, and aggregates. Use it to snapshot reviews for an app without waiting.

Instructions

Creates a public Steam review corpus in the background and immediately returns a new corpus_id for status checks, local queries and aggregates. Each call creates a separate corpus. Defaults to every language, all purchase sources and both sentiments, including off-topic activity and metadata. Metadata includes timestamps, playtime, numeric helpfulness and refunded; refund status does not exclude reviews. Recent/updated traversal has no implicit date window. Fetches share one request lane and 429 cooldown. Saved data is a snapshot; create a new corpus to refresh it. Data stays on the server in schema 2 storage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appidYesSteam application ID as a numeric string
languagesNoReview language list, e.g. ['english', 'schinese']. Default ['all']; including 'all' retrieves every language.
page_sizeNoSteam page size per fetch. Steam allows up to 100.
max_reviewsNoOptional cap for the background fetch. Use null to retrieve the full corpus.
review_typeNoReview polarity to retrieve. Defaults to all reviews.all
purchase_typeNoPurchase source to retrieve. Defaults to all purchase types.all
traversal_modeNoExhaustive traversal uses recent (creation time, default) or updated (modification time), without an implicit date window.recent
chunk_size_reviewsNoHow many reviews to store per persisted chunk.
include_review_metadataNoWhen true, server-stored review chunks keep per-review metadata such as timestamp_created, timestamp_updated, timestamp_dev_responded, and author playtime fields like playtime_at_review and last_played, instead of only review text.
include_offtopic_activityNoWhen true, include off-topic/review-bomb activity in the corpus fetch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.1.1
    • changedInput schema / properties / appid / description
      Previous value: -"Steam application ID"New value: +"Steam application ID as a numeric string"
    • addedInput schema / properties / appid / pattern
      Added value: +"^\\d+$"
    • removedInput schema / properties / language
      Removed value: -{
-  "default": "all",
-  "description": "Language filter for the corpus fetch. Defaults to all languages.",
-  "enum": [
-    "all",
-    "arabic",
-    "bulgarian",
-    "schinese",
-    "tchinese",
-    "czech",
-    "danish",
-    "dutch",
-    "english",
-    "finnish",
-    "french",
-    "german",
-    "greek",
-    "hungarian",
-    "indonesian",
-    "italian",
-    "japanese",
-    "koreana",
-    "norwegian",
-    "polish",
-    "portuguese",
-    "brazilian",
-    "romanian",
-    "russian",
-    "spanish",
-    "latam",
-    "swedish",
-    "thai",
-    "turkish",
-    "ukrainian",
-    "vietnamese"
-  ],
-  "type": "string"
-}
    • addedInput schema / properties / languages
      Added value: +{
+  "default": [
+    "all"
+  ],
+  "description": "Review language list, e.g. ['english', 'schinese']. Default ['all']; including 'all' retrieves every language.",
+  "items": {
+    "enum": [
+      "all",
+      "arabic",
+      "bulgarian",
+      "schinese",
+      "tchinese",
+      "czech",
+      "danish",
+      "dutch",
+      "english",
+      "finnish",
+      "french",
+      "german",
+      "greek",
+      "hungarian",
+      "indonesian",
+      "italian",
+      "japanese",
+      "koreana",
+      "norwegian",
+      "polish",
+      "portuguese",
+      "brazilian",
+      "romanian",
+      "russian",
+      "spanish",
+      "latam",
+      "swedish",
+      "thai",
+      "turkish",
+      "ukrainian",
+      "vietnamese"
+    ],
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array"
+}
    • changedInput schema / properties / traversal_mode / description
      Previous value: -"Cursor traversal mode for exhaustive corpus retrieval. Use \"recent\" or \"updated\"; Steam's \"all\" helpfulness mode does not terminate reliably for full traversal."New value: +"Exhaustive traversal uses recent (creation time, default) or updated (modification time), without an implicit date window."
  2. First observedv1.0.5

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so richly: background execution, immediate corpus_id return, separate corpus per call, snapshot semantics, no implicit date window, shared request lane with 429 cooldown, and server-side schema 2 storage. It also clarifies metadata and refund behavior, giving the agent substantial operational context.

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 front-loaded with the core action and return value, then proceeds through defaults, metadata, traversal, rate limits, and storage. Every sentence carries actionable information, with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex asynchronous corpus-creation tool with ten parameters, no annotations, and no output schema, the description is complete: it explains the return value, background nature, default scope, rate-limit behavior, snapshot semantics, and storage location. Nothing essential for correct invocation or downstream tool selection is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 all ten parameters, setting the baseline at 3. The description still adds meaning beyond the schema by clarifying that refund status does not exclude reviews and that recent/updated traversal has no implicit date window.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence states a specific verb and resource: creates a public Steam review corpus in the background and returns a corpus_id. It distinguishes this from read/status/query/aggregate siblings by making clear that this is the corpus-creation step, not a retrieval or analysis step.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It says the returned corpus_id is for status checks, local queries and aggregates, and that a new corpus is needed to refresh a snapshot. This gives clear usage context, but it does not explicitly name when to choose this over get_steam_review or other alternatives.

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