Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Steam store catalogue

steam_apps_browse
Read-onlyIdempotent

Browse the Steam catalogue page by page and filter apps by type, tags, price, review score, release date, and status to find matching titles.

Instructions

List the whole Steam catalogue page by page, filtered by type, tags, price, review score and release date. Optional inputs: type, tags, excludeTags, status, price and 13 more. Returns a list (use page 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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "steam_apps_browse"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-based). Default: 1.
sortNo`popular` (default) is Steam's popularity order; `name` is A to Z; `appid` is by app id, which is stable and lists the whole catalogue page by page.
tagsNoOnly apps with all of these tag ids, comma-separated, e.g. `1684,19`.
typeNoOnly this kind of item. Without it, every kind is listed.
limitNoResults per page. 1 to 100 for `compact` (default 25); 1 to 1,000 for `ids` (default 100).
priceNoOnly free apps, or only apps that cost money.
fieldsNo`compact` (default) returns app records; `ids` returns only app ids and allows up to 1,000 per page.
statusNo`released` (default), `coming_soon` for apps not out yet, or `any`.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
countryNoCountry the prices are shown for, as an ISO 3166-1 alpha-2 code. Default: `US`.
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.
releasedToNoOnly apps released on or before this date (UTC).
excludeTagsNoLeave out apps with any of these tag ids, comma-separated.
minDiscountNoOnly apps discounted by at least this many percent.
parentAppIdNoOnly DLC and demos of this app.
releasedFromNoOnly apps released on or after this date (UTC).
minReviewScoreNoOnly apps whose Steam review score is at least this, 1 to 9 (9 is overwhelmingly positive). Apps without reviews are left out.
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.
contentDescriptorsNoOnly apps with all of these content descriptor ids, e.g. `3` for adult sexual content.
excludeContentDescriptorsNoLeave out apps with any of these content descriptor ids.

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 readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds pagination behaviour and the list-shaped result, which is genuinely useful, but says nothing about the mandatory context/llm_model handshake or the conversation_id sequencing constraint documented in the schema.

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, front-loaded sentences that state scope first and the result shape second. The 'and 13 more' clause is slightly vague but serves as a useful pointer to the schema; nothing else is wasted.

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?

For a 21-parameter, open-world browse tool with no output schema, the description covers scope and return shape but omits the required-parameter obligations and the pagination limits tied to the `fields` mode. Adequate to call it, thin for calling it correctly on the first try.

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 coverage is 100% with readable enum and default documentation, so the schema does the heavy lifting. The description still adds orientation by naming the primary filter parameters and signalling that 13 more exist, warning the agent to read the full schema rather than assume the listed set is complete.

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?

A specific verb and resource: 'List the whole Steam catalogue page by page', qualified by the filter axes (type, tags, price, review score, release date). It clearly reads as catalogue enumeration rather than lookup, but it never names a sibling such as steam_apps_search to make the browse-vs-search split explicit.

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?

'List the whole Steam catalogue page by page' and 'use page when paginated' imply the enumeration use case, but there is no stated when-not and no pointer to the sibling to use instead when the agent has a specific name or wants suggestions.

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