Retrieve a Steam user's wishlist with optional live prices, discounts, and sale-only filtering. Specify SteamID or profile URL; returns markdown or JSON.
Get a user's Steam wishlist, optionally with live prices and sale status.
| Name | Required | Description | Default |
|---|---|---|---|
| params | Yes |
Changes observed during successful MCP inspections.
v1.18.0Input schema / $defs / ResponseFormatRemoved value: -{
- "description": "Output format for tool responses.",
- "enum": [
- "markdown",
- "json"
- ],
- "title": "ResponseFormat",
- "type": "string"
-}Input schema / $defs / WishlistInput / properties / country_code / titleRemoved value: -"Country Code"Input schema / $defs / WishlistInput / properties / enrich / titleRemoved value: -"Enrich"Input schema / $defs / WishlistInput / properties / limit / titleRemoved value: -"Limit"Input schema / $defs / WishlistInput / properties / on_sale_only / titleRemoved value: -"On Sale Only"Input schema / $defs / WishlistInput / properties / response_format / $refRemoved value: -"#/$defs/ResponseFormat"Input schema / $defs / WishlistInput / properties / response_format / enumAdded value: +[
+ "markdown",
+ "json"
+]Input schema / $defs / WishlistInput / properties / response_format / typeAdded value: +"string"Input schema / $defs / WishlistInput / properties / steamid / defaultRemoved value: -nullInput schema / $defs / WishlistInput / properties / steamid / titleRemoved value: -"Steamid"Input schema / $defs / WishlistInput / titleRemoved value: -"WishlistInput"Input schema / titleRemoved value: -"steam_get_wishlistArguments"Output schema / (root)Previous value: -{
- "properties": {
- "result": {
- "title": "Result",
- "type": "string"
- }
- },
- "required": [
- "result"
- ],
- "title": "steam_get_wishlistOutput",
- "type": "object"
-}New value: +nullv1.14.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds that the tool can optionally fetch live prices and sale status, which is useful behavioral context beyond the annotation. However, it does not disclose that enrichment costs store lookups or mention potential rate limits or failure modes, so it stops at adequate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no filler. It states the action, target, and an optional modifier efficiently. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description gives a clear high-level purpose, but it omits details about output format (markdown/json), user resolution via vanity name or URL, and the meaning of the limit parameter (wishlist priority). The schema covers these, but since there is no output schema, the description could have provided more context about what the agent receives. It is adequate but not fully complete for a tool with several configurable parameters.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With schema description coverage at 0%, the description must compensate for parameter meaning, but it only hints at enrichment and sale status. It does not explain steamid, limit, country_code, response_format, or the dependency between enrich and on_sale_only. The schema itself has rich descriptions, but the tool description adds only a small amount of parameter-related context.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: 'Get a user's Steam wishlist'. It also mentions optional live prices and sale status, which distinguishes it from sibling getters like steam_get_owned_games or steam_get_inventory. The tool is the only wishlist-related sibling, so there is no ambiguity about what it does.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided about when to use this tool versus alternatives. It does not mention how it differs from other user-data getters, nor does it state any conditions (e.g., 'use this when you need wishlist contents, not owned games'). There is no when-not or alternative routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.