Steam MCP Server

Overview Schema Source Related Servers Discussions Admin

Get featured store sections

get_featured

Read-only

Retrieve Steam's featured store sections—specials, top sellers, new releases, and coming soon—in one call to see what's on the store front page.

Instructions

Get the Steam store's featured sections: specials, top sellers, new releases and coming soon (each a list of games with appid and price), all in one call — for a general 'what's on the store front page' overview. For just current discounts use get_specials (lighter), or discover_games for catalog-wide deals with filters. No API key required.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`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`.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`specials`	Yes
`coming_soon`	Yes
`top_sellers`	Yes
`new_releases`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed26 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 / coming_soon / items / properties / final_price / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / coming_soon / items / properties / final_price / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / coming_soon / items / properties / original_price / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / coming_soon / items / properties / original_price / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / coming_soon / items / properties / store_url / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / coming_soon / items / properties / store_url / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / new_releases / items / properties / final_price / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / new_releases / items / properties / final_price / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / new_releases / items / properties / original_price / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / new_releases / items / properties / original_price / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / new_releases / items / properties / store_url / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / new_releases / items / properties / store_url / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / specials / items / properties / final_price / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / specials / items / properties / final_price / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / specials / items / properties / original_price / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / specials / items / properties / original_price / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / specials / items / properties / store_url / anyOf

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

addedOutput schema / properties / specials / items / properties / store_url / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / top_sellers / items / properties / final_price / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / top_sellers / items / properties / final_price / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / top_sellers / items / properties / original_price / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / top_sellers / items / properties / original_price / type
```
Added value: +[
+  "string",
+  "null"
+]
```
removedOutput schema / properties / top_sellers / items / properties / store_url / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / top_sellers / items / properties / store_url / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed4 schema fields changedv0.13.1Aug 17, 2026

addedOutput schema / properties / coming_soon / items / properties / final_price / description

Added value: +"Current price, or null when this section's payload carries no price — which is every `coming_soon` entry (not yet priced, NOT free) and any free-to-play title. Call get_game or get_items on the appid when you need to tell those two apart."

addedOutput schema / properties / new_releases / items / properties / final_price / description

Added value: +"Current price, or null when this section's payload carries no price — which is every `coming_soon` entry (not yet priced, NOT free) and any free-to-play title. Call get_game or get_items on the appid when you need to tell those two apart."

addedOutput schema / properties / specials / items / properties / final_price / description

Added value: +"Current price, or null when this section's payload carries no price — which is every `coming_soon` entry (not yet priced, NOT free) and any free-to-play title. Call get_game or get_items on the appid when you need to tell those two apart."

addedOutput schema / properties / top_sellers / items / properties / final_price / description

Added value: +"Current price, or null when this section's payload carries no price — which is every `coming_soon` entry (not yet priced, NOT free) and any free-to-play title. Call get_game or get_items on the appid when you need to tell those two apart."

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

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already signal read-only and open-world behavior; the description adds that all four sections come in one call, includes appid/price per game, and requires no API key. This adds useful behavioral context beyond the annotations without contradicting them.

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?

Three sentences deliver purpose, contents, use-case guidance, alternatives, and auth requirement with no filler. The core action and included sections are front-loaded in the first sentence.

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?

With only two optional parameters, fully documented schema, an output schema, and strong annotations, nothing needed for correct invocation is missing. Regional/language fallback details that are not in the description are already present 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%, and both country and language have detailed explanations including fallback behavior and typo handling. The description itself does not add parameter-level detail, which is fine because the schema already carries the full burden.

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?

Opens with a specific verb and resource: 'Get the Steam store's featured sections'. It enumerates exactly which sections are included (specials, top sellers, new releases, coming soon) and what data they contain, so an agent knows precisely what this tool returns.

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?

Explicitly defines the intended use as a general front-page overview and names the alternatives: get_specials for current discounts and discover_games for catalog-wide filtered deals. Also notes that no API key is required, removing a common prerequisite question.

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