Skip to main content
Glama

Get game details

get_game
Read-only

Retrieve full Steam store details for any game: description, price, discounts, genres, platforms, release date, ratings, DLC, and PC requirements. Identify game by appid or title.

Instructions

Get full store details for one game: description, price/discount, genres, platforms, release date, developers/publishers, Metacritic, age rating, DLC and PC requirements. Identify the game by appid (from search_games) OR by name — a title is resolved to the closest store match. No API key required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoGame title to look up instead of an appid — resolved to the closest store match. Provide appid OR name; appid wins if both are given.
appidNoSteam appid (from search_games). Provide appid OR name.
countryNoCountry (cc) for prices/currency; overrides STEAM_COUNTRY for this call.
languageNoStore language (e.g. english, russian); overrides STEAM_LANGUAGE for this call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dlcYes
nameNo
typeYes
appidNo
demosYes
priceYes
genresYes
is_freeYes
websiteYes
base_gameYes
platformsYes
store_urlYes
categoriesYes
developersYes
drm_noticeYes
metacriticYes
publishersYes
coming_soonYes
header_imageYes
release_dateYes
required_ageYes
account_noticeYes
metacritic_urlYes
recommendationsYes
short_descriptionYes
achievements_totalYes
controller_supportYes
content_descriptorsYes
pc_requirements_minYes
supported_languagesYes
achievements_highlightedYesA small keyless sample of named achievements Steam highlights for this game, not the full list — for every achievement with rarity and a hidden flag, use get_game_achievements instead.
Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint. Description adds that no API key is needed and how name resolution works. No contradictions; adds value beyond 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?

Three sentences; first lists return fields, second explains input options, third states auth requirement. Somewhat dense but no fluff; could be slightly more structured.

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 an output schema exists (not shown) and schema coverage 100%, the description covers purpose, input, behavior, and auth. Complete for agent decision-making.

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%, baseline 3. Description adds clarifying behavior: appid wins if both given, name is fuzzy-matched. This goes beyond schema.

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 explicitly lists the returned data (description, price/discount, genres, etc.) and distinguishes itself from sibling tools like search_games (which returns a list) and get_prices (price only). Verb 'Get' + resource 'full store details' clear.

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

Usage Guidelines4/5

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

Description states input options (appid or name) and that name resolves to closest match. It also notes no API key required. While it doesn't explicitly state when not to use, the sibling list provides context; implicit alternatives exist.

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

Install Server

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