Skip to main content
Glama

Get owned games

get_owned_games
Read-only

Retrieve a player's owned Steam games with playtime hours, and optionally verify ownership of specific appids even if they fall outside the top 50.

Instructions

List the games a player owns with playtime (hours), most-played first (the games list is capped to the top 50 by playtime — a lightly-played or unplayed game may not appear there). To reliably check whether the player owns one or more SPECIFIC appids regardless of that cap — 'do I own game X' — pass check_appids; the owns field then checks the FULL, uncapped library, with each result's own playtime_hours (null if not owned). For the last two weeks of play instead of the all-time library, use get_recently_played. For checking a FRIEND's ownership instead of the player's own, use find_friends_who_own. Requires STEAM_API_KEY and a public profile + game-details visibility. Get the SteamID64 from resolve_vanity_url.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
steamidNo17-digit SteamID64. Omit to use the STEAM_ID configured on the server. Convert a vanity/custom URL name with resolve_vanity_url first.
check_appidsNoSteam appids to check ownership of (1-50), regardless of the top-50-by-playtime cap on `games`. Adds an `owns` field: [{appid, owned, playtime_hours}]. One upstream gap to know about: Steam omits free-to-play titles the player owns but has NEVER launched, so those report owned:false. A private profile reports no `owns` at all (ownership unknown) rather than a false owned:false.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Install Server

TDQS

A5/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the top-50-by-playtime cap on `games`, the uncapped behavior of check_appids, the free-to-play never-launched omission, and the private-profile reporting ('no `owns` at all'). These are crucial behavioral caveats not evident from annotations alone.

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?

Every sentence serves a purpose: main capability, cap caveat, ownership-check alternative, two sibling differentiators, requirements, and input resolution. Information-dense without redundancy, and the most important action ('List...') is front-loaded.

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 the output schema exists and annotations cover safety, the description still adds essential context: alternatives, limits, prerequisites, and edge cases. The agent can confidently select, invoke, and interpret results without external documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema already describes both parameters with 100% coverage, the description enriches them with real-world usage context: check_appids is positioned as a reliable ownership test, explains the `owns` result shape, and highlights edge cases (free-to-play, private profiles). It also adds practical advice for the `steamid` parameter via resolve_vanity_url.

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?

Description opens with a specific verb+resource+scope: 'List the games a player owns with playtime (hours), most-played first.' It also explicitly contrasts with sibling tools (get_recently_played, find_friends_who_own), making its unique purpose unmistakable.

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?

Provides explicit when-to-use guidance: use check_appids for specific ownership checks, use get_recently_played for two-week activity, and use find_friends_who_own for friends. Also states prerequisite visibility requirements (public profile + game-details visibility) and how to obtain the required SteamID64.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Grinv/steam-games-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server