Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

datasets_playstation_games_search

Search the public PlayStation Store catalog to find games, editions, and add-ons by genre, price, platform, and more. Filter results by free titles, sales, or subscription inclusion.

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)
Behavior4/5

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

The description explains result structure (one row per SKU, grouping by concept_id/np_title_id) and documents enums for price_tier and sort. However, without annotations, it does not explicitly confirm read-only behavior or disclose rate limits, though search implies non-destructive use.

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 concise and front-loaded with the main purpose, but it repeats some enum information from the schema, which could be trimmed. Still, it is efficiently structured.

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

Completeness2/5

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

Given 28 parameters and no output schema, the description does not sufficiently describe return fields, pagination limits, or expected output format. It lacks completeness for an agent to fully understand tool behavior without additional context.

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%, but the description adds value by explaining the meaning of concept_id/np_title_id grouping and detailing price_tier and sort enum values, going beyond the schema's parameter 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 clearly identifies the tool as a search for PlayStation games dataset, specifying it searches the crawled public PlayStation Store catalog. It distinguishes itself from sibling tools like datasets_playstation_games_item by focusing on searching with multiple filters.

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 like datasets_playstation_games_item or datasets_playstation_games_facets. The description lacks explicit context for choosing this tool.

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/Crawlora-org/crawlora-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server