Steam MCP Server

Overview Schema Source Related Servers Discussions Admin

Search games

search_games

Read-only

Find Steam games by partial or approximate title to get appids, prices, Metacritic scores, platforms, and store URLs in relevance order.

Instructions

Search the Steam store by title — term can be partial or approximate, not an exact match; returns matches with their appid (needed by the other game tools), the game's own price, Metacritic score, platforms, type (game, dlc, music for a soundtrack, demo, …) and a clickable store_url, in Steam's relevance order. total is Steam's full match count; limit returns up to 100 of them (there is no paging past that, so refine the term if the game you want isn't listed). Prices are Steam's formatted strings with the currency symbol (no separate currency code); null for free-to-play or unpriced games. Returns games only by default; set games_only=false to include DLC, soundtracks, demos and other store items. For review %, Steam Deck status or tags, pass the appids to get_items. No API key required.

Input Schema

Name	Required	Description
`term`	Yes	Game title to search for.
`limit`	No	How many matches to return (1-100). Default 10.
`country`	No	Country (cc) for prices/currency and regional availability; overrides STEAM_COUNTRY for this call. Must be a real Steam store region — the two-letter shape is all that's checked here, and Steam answers an unrecognized code with US prices rather than an error, so a typo returns plausible numbers for the wrong country.
`language`	No	Store language for the text fields. Use Steam's own language NAME — english, russian, schinese/tchinese — not an ISO code like en/ru/zh. An unrecognized value is never an error: text comes back in English and any `tags` list comes back EMPTY, which reads as 'this game has no tags' rather than as a bad language. (Filtering BY tags is the one loud case — it fails outright.) Overrides STEAM_LANGUAGE for this call. This is the content language only — prices and regional availability follow `country`.
`games_only`	No	true (default) = games only; false = also DLC, soundtracks, demos, software and other store items (e.g. to find a game's DLC). Filtered by Steam itself, so `limit` is still filled and `total` counts only what this includes.

Output Schema

Name	Required	Description
`total`	Yes	Steam's total number of matches for the term — often more than `returned`.
`results`	Yes
`returned`	Yes	Results in this response (at most the requested `limit`).

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv0.17.0Oct 25, 2026

addedInput schema / properties / games_only

Added value: +{
+  "default": true,
+  "description": "true (default) = games only; false = also DLC, soundtracks, demos, software and other store items (e.g. to find a game's DLC). Filtered by Steam itself, so `limit` is still filled and `total` counts only what this includes.",
+  "type": "boolean"
+}

addedInput schema / properties / limit

Added value: +{
+  "default": 10,
+  "description": "How many matches to return (1-100). Default 10.",
+  "exclusiveMinimum": 0,
+  "maximum": 100,
+  "type": "integer"
+}

changedOutput schema / properties / results / items / properties / name / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / results / items / properties / price / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "currency": {
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "discount_percent": {
-        "type": "number"
-      },
-      "final": {
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "initial": {
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "required": [
-      "currency",
-      "final",
-      "initial",
-      "discount_percent"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "discount_percent": {
+        "type": "number"
+      },
+      "final": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "initial": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "final",
+      "initial",
+      "discount_percent"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / results / items / properties / price / description

Added value: +"This game's own price; null when free to play or not priced (unreleased)."

addedOutput schema / properties / results / items / properties / type / description

Added value: +"Store item type: game, dlc, music (soundtrack), demo, software, video, …"

changedOutput schema / properties / results / items / required

Previous value: -[
-  "type",
-  "price",
-  "metascore",
-  "platforms",
-  "store_url"
-]New value: +[
+  "appid",
+  "name",
+  "type",
+  "price",
+  "metascore",
+  "platforms",
+  "store_url"
+]

addedOutput schema / properties / returned

Added value: +{
+  "description": "Results in this response (at most the requested `limit`).",
+  "type": "number"
+}

addedOutput schema / properties / total / description

Added value: +"Steam's total number of matches for the term — often more than `returned`."

changedOutput schema / required

Previous value: -[
-  "total",
-  "results"
-]New value: +[
+  "total",
+  "returned",
+  "results"
+]

Changed9 schema fields changedv0.14.0Sep 27, 2026

changedInput schema / properties / country / description

Previous value: -"Country (cc) for prices/currency; overrides STEAM_COUNTRY for this call."New value: +"Country (cc) for prices/currency and regional availability; overrides STEAM_COUNTRY for this call. Must be a real Steam store region — the two-letter shape is all that's checked here, and Steam answers an unrecognized code with US prices rather than an error, so a typo returns plausible numbers for the wrong country."

changedInput schema / properties / language / description

Previous value: -"Store language (e.g. english, russian); overrides STEAM_LANGUAGE for this call."New value: +"Store language for the text fields. Use Steam's own language NAME — english, russian, schinese/tchinese — not an ISO code like en/ru/zh. An unrecognized value is never an error: text comes back in English and any `tags` list comes back EMPTY, which reads as 'this game has no tags' rather than as a bad language. (Filtering BY tags is the one loud case — it fails outright.) Overrides STEAM_LANGUAGE for this call. This is the content language only — prices and regional availability follow `country`."

removedOutput schema / properties / results / items / properties / metascore / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / results / items / properties / metascore / type
```
Added value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / results / items / properties / price / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "currency": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "discount_percent": {
-        "type": "number"
-      },
-      "final": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "initial": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "required": [
-      "currency",
-      "final",
-      "initial",
-      "discount_percent"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "currency": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "discount_percent": {
+        "type": "number"
+      },
+      "final": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "initial": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "currency",
+      "final",
+      "initial",
+      "discount_percent"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / results / items / properties / store_url / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / results / items / properties / store_url / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / results / items / properties / type / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / results / items / properties / type / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed1 schema field changedv0.12.1Jul 30, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
Addedv0.10.2Jul 22, 2026
Removedv0.9.0Jul 18, 2026
Addedv0.8.0Jul 17, 2026
Removedv0.8.0Jul 17, 2026
First observedv0.1.0Jun 29, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses relevance ordering, the 100-result cap, total versus limit semantics, formatted/null price behavior, and the effect of games_only on filtering and totals. These are meaningful behavioral traits not captured by annotations.

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?

The description is front-loaded with purpose and key constraints, and most sentences carry useful information. It is somewhat long and overlaps with schema details, but the density is justified by several important API quirks.

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?

Given that an output schema exists, the description need not document return values exhaustively. It still provides enough context about returned fields, ordering, price formatting, and filtering behavior for an agent to call the tool correctly.

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%, so the schema already documents all five parameters. The description still adds useful meaning for term matching, limit paging limits, and games_only/total interactions, though it does not add much to the already detailed country and language parameters.

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 description states a specific verb and resource: searching the Steam store by title. It also distinguishes the tool from alternatives by explaining that get_items should be used for review percentages, Steam Deck status, or tags.

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

Usage Guidelines5/5

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

It explicitly covers when to use this tool, when to set games_only=false, and where to go for related data via get_items. It also gives practical guidance such as refining the term if the wanted game is not listed because there is no paging past 100 results.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.