Skip to main content
Glama
icue

Steam Review and Forum MCP

by icue

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
STEAM_FORUM_EXPORT_DIRNoDirectory to store saved forum thread datasets. Defaults to a package-relative directory..steam-forum-exports/
STEAM_REVIEW_EXPORT_DIRNoDirectory to store saved review datasets. Defaults to a package-relative directory..steam-review-exports/
STEAM_FORUM_EXPORT_TTL_HOURSNoTime-to-live in hours for stored forum exports. Exports older than this are cleaned up.24
STEAM_REVIEW_EXPORT_TTL_HOURSNoTime-to-live in hours for stored review exports. Exports older than this are cleaned up.24

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_server_infoA

Returns the name and package version of the running MCP server process.

get_steam_reviewA

Reads a page of public Steam reviews directly from Steam. Defaults to helpful ranking, every language, all purchase sources and both sentiments, including off-topic activity. Use recent for new feedback, updated for modifications, and a background corpus for large analyses. fetch_all automatically uses recent for helpful requests. Optional review_details contains timestamps, playtime, numeric helpfulness and refunded metadata; refunds are not filtered. All review fetches share request spacing and 429 cooldown. Anonymous responses may be cached by Steam for up to 10 minutes.

get_steam_game_infoB

Retrieves English game metadata for a specific app, including release date, developers, publishers, genres, and price overview. The detailed description is cleaned into plain text for LLM consumption.

list_steam_forum_sectionsB

Lists the available public Steam Community discussion sections and forum-like app hub surfaces for a game's hub, including each section's numeric id when applicable and URL.

list_steam_forum_topicsA

Lists topics from a game's public Steam Community discussion section or compatible app hub forum surface. Supports section selection for discussions and listing pagination via ?fp=N. Each topic's last_activity_timestamp and last_activity_display describe its latest reply or listing activity, never its original publication time. Call get_steam_forum_topic and use topic.original_post_timestamp before making publication-date claims. On some app hub surfaces such as Events & Announcements, Steam omits row-level author and preview markup, so those fields may be null in listing results.

get_steam_forum_topicA

Fetches a public Steam Community topic, including the original post and replies. The returned topic.original_post_timestamp is the original topic or hydrated announcement publication time; reply items keep their own timestamp fields. Use this field, not listing activity, for publication-date claims. Supports General Discussions topics and compatible app hub forum surfaces such as Events & Announcements, with reply pagination via ?ctp=N. When an Events & Announcements thread only contains a stub that links to the real announcement article, the server follows that link and returns the announcement body and publication time when possible.

create_steam_forum_topic_corpusA

Starts a server-side background fetch for a public Steam Community topic, stores replies in server-managed chunks, and returns an opaque identifier immediately for later status checks and chunk reads. Supports discussion topics and compatible app hub forum surfaces. When an Events & Announcements thread only contains a stub that links to the real announcement article, the server follows that link and stores the announcement body as the topic content when possible. Data stays on the server and is not exported to the caller as files.

get_steam_forum_topic_corpus_statusB

Returns the persisted manifest and progress summary for a server-side Steam Community topic fetch.

read_steam_forum_topic_corpus_chunkC

Reads one stored reply chunk from a previously created server-side Steam Community topic fetch.

create_steam_review_corpusA

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.

get_steam_review_corpus_statusA

Returns saved review corpus progress, chunks, stop reason and errors. running means fetching or queued; waiting means rate-limit cooldown with next_retry_at as a UTC ISO timestamp. Polling does not bypass cooldown. total_reviews_expected is Steam's reported matching count, not proof of completeness. Resumes interrupted schema 2 jobs; completed corpora stay local and are not refreshed. Unsupported storage returns UNSUPPORTED_CORPUS_VERSION; recreate the corpus. Expired or missing IDs return not_found.

query_steam_review_corpusA

Queries persisted schema 2 review chunks by text, language, date, sentiment and playtime, with pagination, field selection and optional timestamp ordering. Playtime thresholds are minutes. Timestamp, sentiment, playtime filtering and sorting require metadata; unavailable values are null. Fields include numeric weighted_vote_score and refunded; refund status does not filter results. Counts cover committed chunks, which may be partial or capped; inspect corpus status and stop reason. Completed corpora are read locally without refresh; create a new corpus for updated data. Interrupted jobs may resume while respecting cooldown. Unsupported formats return UNSUPPORTED_CORPUS_VERSION.

aggregate_steam_review_corpusA

Aggregates committed schema 2 review chunks using text, language, date, sentiment and playtime filters. Returns review counts, positive/negative counts and ratios, average playtimes in minutes, language breakdowns and optional UTC day/week/month buckets (weeks start Monday). Requires metadata. Refund status does not exclude, group or reweight records. Results cover saved data, which can be partial or capped. Completed corpora are read locally without refresh; create a new corpus for updated data. Interrupted jobs may resume while respecting cooldown. Unsupported formats return UNSUPPORTED_CORPUS_VERSION.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 13 tools

Disambiguation4/5

The tools largely target distinct resources and actions, with clear separation between direct review/forum fetches and background corpus lifecycle operations. However, the multiple corpus-related tools for reviews and forums could be confused at a glance, and get_server_info is an unrelated utility that slightly dilutes focus.

Naming Consistency4/5

Most names follow a predictable snake_case verb_noun pattern with the 'steam' domain inserted after the verb, such as get_steam_review and create_steam_review_corpus. The main deviation is get_server_info, which lacks the steam prefix, and read_steam_forum_topic_corpus_chunk uses 'read' while similar retrieval tools use 'get'.

Tool Count5/5

With 13 tools, the set is well-scoped for a dual-domain server covering Steam reviews and forums. Each tool appears to serve a distinct lifecycle role, from direct fetches to background corpus creation, status polling, querying, and aggregation.

Completeness4/5

The surface covers core read-only workflows for Steam reviews and forums, including direct access, corpus creation, status checks, querying, aggregation, and forum listing/reading. Minor gaps include no tool to list or delete existing corpora and no forum search beyond section/topic listing, but agents can work around these limitations.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive