getcheapgames

Latest news, guides, reviews and deals

list_news

Read-only

Return getcheapgames' latest editorial posts, newest first: news, buying guides, reviews, deals roundups and videos. Use it for gaming news or the site's articles; for prices use search_games or get_game_offers. tag keeps one kind, and query keeps posts whose title or summary contains its words, ignoring case, among the newest 48; both combine. country picks the language, a post's translation where it has one and English otherwise; none found gives an empty list.

Input Schema

Name	Required	Description
`tag`	No	Only posts of this kind: news, guide, review, deals or video.
`limit`	No	Posts to return, 1-12. Defaults to 5.
`query`	No	Words to find in a post's title or summary, e.g. "GTA 6".
`country`	No	Two-letter market code, any case, e.g. de, gb, us, br or pl (40 markets). It decides the currency prices come back in, which keys count as region-locked, and the market every link opens in. Omitted or unsupported codes fall back to ie (Ireland, euro).

Output Schema

Name	Required	Description	Default
`tag`	No
`posts`	Yes
`query`	No
`market`	No
`pageUrl`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 19, 2026

changedInput schema / properties / country / description

Previous value: -"Two-letter market code, e.g. de, gb, us, br. Decides the currency, which keys count as region-locked and the market every link points into. Defaults to ie (euro)."New value: +"Two-letter market code, any case, e.g. de, gb, us, br or pl (40 markets). It decides the currency prices come back in, which keys count as region-locked, and the market every link opens in. Omitted or unsupported codes fall back to ie (Ireland, euro)."

changedInput schema / properties / limit / description

Previous value: -"How many posts to return. Defaults to 5."New value: +"Posts to return, 1-12. Defaults to 5."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "market": {
+      "type": "string"
+    },
+    "pageUrl": {
+      "type": "string"
+    },
+    "posts": {
+      "items": {
+        "properties": {
+          "imageUrl": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "kind": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "publishedAt": {
+            "description": "ISO 8601 time.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "readingMinutes": {
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "slug": {
+            "type": "string"
+          },
+          "summary": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "slug",
+          "title",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "query": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "tag": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "posts"
+  ],
+  "type": "object"
+}

First observedOct 13, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint, destructiveHint=false), so the description uses its space for behavior the annotations cannot convey: newest-first ordering, case-insensitive query matching restricted to the newest 48 posts, tag/query combining, and the translation/English fallback plus empty-list result when nothing is found.

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?

It is front-loaded with the verb and resource, and every sentence carries information with no filler. It is on the dense/long side for a list tool, packing filtering, combination, and fallback rules into one paragraph, though nothing is genuinely wasted.

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?

An output schema exists, so return-value shape needn't be restated; the description instead covers everything the agent needs to call it correctly: ordering, filtering semantics, parameter interaction, country/language fallback, and the empty-result case. Complete for a read-only, four-optional-parameter list tool.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: `query` matches title *or* summary, case-insensitively, and only within the newest 48 posts; `tag` and `query` combine; `country` selects a post's translation when available, otherwise English. None of this is in the field descriptions.

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+resource ('Return getcheapgames' latest editorial posts') and enumerates the content scope (news, guides, reviews, deals, videos). It explicitly distinguishes this tool from search_games and get_game_offers, which cover pricing, so an agent can route without opening the schema.

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 states when to use it ('for gaming news or the site's articles') and names the exact alternative tools for the competing need ('for prices use search_games or get_game_offers'). The tag/query combination rules and country behavior are also spelled out rather than left to inference.

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

All getcheapgames tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.