Steam MCP Server

Overview Schema Source Related Servers Discussions Admin

Get a player's followed games

get_followed_games

Read-only

List games a Steam player follows by SteamID64, returning app IDs and store URLs. Works only with public profiles; no API key required. Use resolve_vanity_url to convert names first.

Instructions

List the games a player 'follows' on the Steam store, by SteamID64 — a lighter opt-in (get sale/update notifications) that's separate from the wishlist; many players follow more games than they wishlist. No API key required, but the follows/profile must be public — otherwise it returns found:false, which is ALSO what a public account following nothing returns; read reason to tell those apart. Returns appids + store_url only (no price/name), capped at 200 in whatever order Steam sends them — unlike every other capped list here there is no ranking, so a game past the cut is not 'less followed' (check returned vs total); pass the appids to get_items for price, review % and compat. Convert a vanity name with resolve_vanity_url first (that conversion itself needs STEAM_API_KEY, even though this tool doesn't).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`steamid`	No	17-digit SteamID64. Omit to use the STEAM_ID configured on the server. Convert a vanity/custom URL name with resolve_vanity_url first.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.14.0Sep 27, 2026

changedOutput schema / oneOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "found": {
-        "const": false,
-        "type": "boolean"
-      },
-      "games": {
-        "items": {
-          "not": {}
-        },
-        "type": "array"
-      },
-      "reason": {
-        "type": "string"
-      },
-      "total": {
-        "const": 0,
-        "type": "number"
-      }
-    },
-    "required": [
-      "found",
-      "reason",
-      "total",
-      "games"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "found": {
-        "const": true,
-        "type": "boolean"
-      },
-      "games": {
-        "items": {
-          "additionalProperties": false,
-          "properties": {
-            "appid": {
-              "type": "number"
-            },
-            "store_url": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            }
-          },
-          "required": [
-            "appid",
-            "store_url"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "returned": {
-        "type": "number"
-      },
-      "total": {
-        "type": "number"
-      }
-    },
-    "required": [
-      "found",
-      "total",
-      "returned",
-      "games"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "found": {
+        "const": false,
+        "type": "boolean"
+      },
+      "games": {
+        "items": {
+          "not": {}
+        },
+        "type": "array"
+      },
+      "reason": {
+        "type": "string"
+      },
+      "total": {
+        "const": 0,
+        "type": "number"
+      }
+    },
+    "required": [
+      "found",
+      "reason",
+      "total",
+      "games"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "found": {
+        "const": true,
+        "type": "boolean"
+      },
+      "games": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "appid": {
+              "type": "number"
+            },
+            "store_url": {
+              "type": [
+                "string",
+                "null"
+              ]
+            }
+          },
+          "required": [
+            "appid",
+            "store_url"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "returned": {
+        "type": "number"
+      },
+      "total": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "found",
+      "total",
+      "returned",
+      "games"
+    ],
+    "type": "object"
+  }
+]

Changed3 schema fields changedv0.12.1Jul 30, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

removedOutput schema / anyOf

Removed value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "found": {
-        "const": false,
-        "type": "boolean"
-      },
-      "games": {
-        "items": {
-          "not": {}
-        },
-        "type": "array"
-      },
-      "reason": {
-        "type": "string"
-      },
-      "total": {
-        "const": 0,
-        "type": "number"
-      }
-    },
-    "required": [
-      "found",
-      "reason",
-      "total",
-      "games"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "found": {
-        "const": true,
-        "type": "boolean"
-      },
-      "games": {
-        "items": {
-          "additionalProperties": false,
-          "properties": {
-            "appid": {
-              "type": "number"
-            },
-            "store_url": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            }
-          },
-          "required": [
-            "appid",
-            "store_url"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "returned": {
-        "type": "number"
-      },
-      "total": {
-        "type": "number"
-      }
-    },
-    "required": [
-      "found",
-      "total",
-      "returned",
-      "games"
-    ],
-    "type": "object"
-  }
-]

addedOutput schema / oneOf

Added value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "found": {
+        "const": false,
+        "type": "boolean"
+      },
+      "games": {
+        "items": {
+          "not": {}
+        },
+        "type": "array"
+      },
+      "reason": {
+        "type": "string"
+      },
+      "total": {
+        "const": 0,
+        "type": "number"
+      }
+    },
+    "required": [
+      "found",
+      "reason",
+      "total",
+      "games"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "found": {
+        "const": true,
+        "type": "boolean"
+      },
+      "games": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "appid": {
+              "type": "number"
+            },
+            "store_url": {
+              "anyOf": [
+                {
+                  "type": "string"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            }
+          },
+          "required": [
+            "appid",
+            "store_url"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "returned": {
+        "type": "number"
+      },
+      "total": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "found",
+      "total",
+      "returned",
+      "games"
+    ],
+    "type": "object"
+  }
+]

Addedv0.10.4Jul 26, 2026
Removedv0.10.2Jul 22, 2026
Addedv0.10.2Jul 22, 2026
Removedv0.8.0Jul 17, 2026
Addedv0.7.0Jul 16, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description adds substantial behavior beyond annotations: no API key required, public profile requirement, the found:false ambiguity and how to resolve it with reason, 200-item cap, no ranking semantics, returned vs total, and the limited return fields. This is exactly the kind of context agents need.

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?

The description is long but every sentence carries unique operational information: purpose, key requirement, ambiguity caveat, return shape, cap/ranking behavior, and linked tools. The core purpose is front-loaded, and later details earn their place.

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?

For a tool with one optional parameter and an output schema, the description covers everything an agent needs: required auth, failure modes, list semantics, how to interpret results, and next-step tool routing. Nothing critical is missing.

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?

The schema already fully describes the steamid parameter, including the 17-digit format, omission behavior, and vanity URL conversion. The description repeats this rather than adding new parameter-level semantics, so the high schema coverage baseline of 3 is appropriate.

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 opens with a specific verb and resource: 'List the games a player follows on the Steam store, by SteamID64.' It also distinguishes the tool from the wishlist concept, making it clear this is about follow notifications rather than wishlisted games.

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 says when this tool is appropriate (no API key, public profile required), when to use an alternative (get_items for prices, resolve_vanity_url for vanity names), and clarifies that the follows list is separate from the wishlist. It also warns about the 'no ranking' difference from other capped list tools.

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