Skip to main content
Glama

Search Video Games

rawg.games.search
Read-onlyIdempotent

Search 800K+ video games — filter by genre, platform, release date, Metacritic score, with ratings, screenshots, and store links (RAWG)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination (default 1)
datesNoFilter by release date range YYYY-MM-DD,YYYY-MM-DD (e.g. "2024-01-01,2024-12-31")
genresNoFilter by genre IDs — comma-separated (e.g. "4" for action, "5" for RPG, "4,5" for both)
searchNoSearch query for games (e.g. "The Witcher", "Red Dead Redemption")
orderingNoSort field: name, released, added, created, updated, rating, metacritic. Prefix with "-" for descending (e.g. "-rating")
page_sizeNoNumber of results per page (default 20, max 40)
platformsNoFilter by platform IDs — comma-separated (e.g. "4" for PC, "187" for PS5, "186" for Xbox Series)
metacriticNoFilter by Metacritic score range "min,max" (e.g. "80,100" for highly rated)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPresent only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
resultNoTool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds that results include 'ratings, screenshots, and store links', providing useful behavioral context beyond annotations. No contradictions.

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?

Single sentence, front-loaded with key information. No wasted words; effectively conveys purpose and features.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 8 parameters all documented, output schema exists, and description mentions result contents. Minor missing: no explicit pagination hint, but parameters cover it. Overall sufficient for a search tool.

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 coverage is 100% with detailed parameter descriptions. The tool description summarizes filter options but does not add significant new meaning beyond what the schema provides. Baseline 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?

Clearly states the verb 'Search' and the resource 'video games' with scope '800K+'. Lists key filters and result features, distinguishing it from sibling tools like rawg.games.details.

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

Usage Guidelines3/5

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

Implies usage for general search with filters, but does not explicitly state when to use this tool over alternatives like rawg.games.details or rawg.games.screenshots. No exclusions or when-not-to-use guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.