Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_playstation_games_search

Search the public PlayStation Store catalog for games, editions, and add-ons; filter by title, publisher, genre, price, discount, platform, region, rating, and release date, then sort results.

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.

Input Schema

TableJSON 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

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the disclosure burden. It does add useful behavior context: the data is crawled, stored in a search index, and row granularity is per SKU with concept_id/np_title_id grouping. It does not disclose result shape, pagination behavior, read-only safety, or how filters combine, which remains a gap for a 28-parameter tool.

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?

The description is compact and front-loaded, opening with the core verb and resource. Every clause adds something: data source, row granularity, and enum context. There is no filler or duplication beyond the enum lists, which are somewhat redundant with the schema but not bloating.

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

Completeness3/5

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

For a complex 28-parameter search tool with no output schema, the description gives useful dataset context but stops short of explaining return values, pagination limits already partially in schema, or how multiple filters interact. It also doesn't route the agent to sibling item/facets tools for complementary needs. It is adequate for selecting the tool but not fully complete.

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%, so the baseline is 3. The description mostly re-lists the price_tier and sort enum values that already appear in the schema, adding little semantic value. The only genuine addition is the explanation of concept_id/np_title_id as grouping keys, but it does not compensate enough to raise the score.

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?

The description leads with 'Search PlayStation games dataset,' a specific verb plus resource, and further clarifies it searches a crawled public PlayStation Store catalog. It adds row-level semantics (one row per product SKU; concept_id/np_title_id grouping), making the tool's purpose concrete. However, it doesn't explicitly distinguish itself from sibling tools like datasets_playstation_games_item or playstation_search.

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?

No guidance is provided on when to use this tool versus alternatives such as datasets_playstation_games_item, datasets_playstation_games_facets, or playstation_search. There are no exclusions, prerequisites, or pointers to complementary tools. The search intent is implied but never stated as a decision rule.

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