Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

datasets_playstation_games_search

Search PlayStation games dataset. Searches the crawled public PlayStation Store catalog stored in a search index. One row per product SKU (game, edition or add-on); concept_id / np_title_id group a title's SKUs.

Instructions

Search PlayStation games dataset. Searches the crawled public PlayStation Store catalog stored in a search index. One row per product SKU (game, edition or add-on); concept_id / np_title_id group a title's SKUs. price_tier enum: free, under_5, 5_to_10, 10_to_20, 20_to_40, 40_to_60, 60_plus. Sort enum: relevance, rating_desc, reviews_desc, price_asc, price_desc, discount_desc, release_desc, release_asc. Billing: this search costs 1 credit per record returned, with a minimum of 2 (an empty result costs 2, a full page of 100 costs 100).

Input Schema

NameRequiredDescriptionDefault
qNoFull-text query over name and publisher, max 256 characters
pageNoPage number, defaults to 1
sortNoSort enum: relevance, rating_desc, reviews_desc, price_asc, price_desc, discount_desc, release_desc, release_asc
genreNoExact genre filter (e.g. Action, Role Playing Games), max 128 characters
regionNoExact store region (country code) filter, max 128 characters
run_idNoExact crawl run-id filter, max 128 characters
is_freeNoFilter by free flag
on_saleNoFilter by titles currently discounted (discount_pct > 0)
brandingNoExact subscription/service-branding filter (e.g. PS_PLUS, EA_PLAY, UBISOFT_PLUS), max 128 characters
is_addonNoFilter: true returns add-ons/DLC/currency, false returns games and editions
platformNoExact platform filter: PS4 or PS5
page_sizeNoPage size, defaults to 20 and maxes at 100; page * page_size must be <= 10000
publisherNoExact publisher filter, max 128 characters
concept_idNoExact concept id filter (groups all SKUs of a title), max 128 characters
price_tierNoPrice-tier enum: free, under_5, 5_to_10, 10_to_20, 20_to_40, 40_to_60, 60_plus
coming_soonNoFilter for pre-release / not-yet-purchasable titles
np_title_idNoExact np_title_id filter, max 128 characters
classificationNoExact classification filter: FULL_GAME, PREMIUM_EDITION, GAME_BUNDLE, ADD_ON_PACK, VIRTUAL_CURRENCY, LEVEL, OTHER
content_ratingNoExact content-rating authority filter (e.g. ESRB, PEGI), max 128 characters
min_star_countNoMinimum number of star ratings
max_price_valueNoMaximum current price in minor units (e.g. cents)
min_price_valueNoMinimum current price in minor units (e.g. cents)
min_star_ratingNoMinimum average star rating, 0 through 5
max_release_yearNoMaximum release year
min_discount_pctNoMinimum discount percent, 0 through 100
min_release_yearNoMinimum release year
content_descriptorNoExact content-descriptor filter (e.g. Blood, Violence, In-Game Purchases, Users Interact), max 128 characters
is_tied_to_subscriptionNoFilter for titles included with a subscription (e.g. free with PS Plus)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / price_tier / enum
      Added value: +[
      +  "free",
      +  "under_5",
      +  "5_to_10",
      +  "10_to_20",
      +  "20_to_40",
      +  "40_to_60",
      +  "60_plus"
      +]
    • addedInput schema / properties / sort / enum
      Added value: +[
      +  "relevance",
      +  "rating_desc",
      +  "reviews_desc",
      +  "price_asc",
      +  "price_desc",
      +  "discount_desc",
      +  "release_desc",
      +  "release_asc"
      +]
  2. Addedv1.5.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and delivers unusually valuable operational detail: the billing model (1 credit per record, minimum 2, empty result costs 2, a full 100-record page costs 100). This directly affects how an agent should size queries. It does not discuss auth or return/pagination specifics beyond the schema, but the cost disclosure is significant added context.

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?

Front-loaded with the core purpose, then data model, then enums, then billing. Every sentence adds something, though the enum restatements duplicate the schema slightly and the block is dense. Efficient overall.

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?

For a 28-parameter, no-required search with full schema coverage and no output schema, the description supplies the missing dimension: what a result row represents and the cost per call. An agent has enough to call it correctly, with the only gap being routing guidance relative to sibling tools.

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%, so the baseline is 3; the description goes beyond by explaining the data model that gives meaning to parameters (concept_id/np_title_id group a title's SKUs) and restating the price_tier and sort enums. The row-grain explanation adds real semantic value the schema alone does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search PlayStation games dataset', the crawled PlayStation Store catalog in a search index) and clarifies the row grain (one product SKU per row, concept_id/np_title_id group a title's SKUs). It does not explicitly name the sibling datasets_playstation_games_item or facets, but the purpose is unambiguous.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no mention of alternatives such as the item or facets sibling tools. The data-model note implies the tool returns SKU-level search results, but the agent is left to infer when this search is preferred over the facet/item endpoints.

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

Deploy Server

Other Tools