Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

playstation_browse

Browse PlayStation Store's all-games grid with pagination. Get per-item prices, platforms, media, and filter facets by region and language.

Instructions

Browse the PlayStation Store all-games grid. Returns a page of the PlayStation Store "all games" grid with per-item price, platforms, and media, plus the available filter facets (price, genre, platform, subscription, content type, etc.) with value counts. Pass page to advance; next_page is set when more results exist. cc selects the store region (and price currency); l accepts a language code or locale such as en or en-US, with the locale's primary language used for text. Credential-free public PlayStation Store data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lNoLanguage code
ccNoStore country code (ISO, selects currency)
pageNo1-based page number

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden, and it does well: it reveals response contents, pagination via next_page, region/currency behavior of cc, language/locale behavior of l, and that the endpoint is credential-free public data. It could add default-page behavior or more return-structure detail, but it is substantially transparent for a read-only browse tool.

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?

The description is four focused sentences with no filler. It front-loads the core purpose and return contents, then efficiently covers pagination, parameters, and authentication expectations. Each sentence earns its place.

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 no output schema and no annotations, the description covers purpose, return contents, pagination, parameter behavior, and credential-free access. It lacks explicit guidance on choosing between the many PlayStation sibling tools and omits default page behavior, but an agent has enough to call and interpret the tool correctly.

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 the schema by explaining pagination semantics ('Pass page to advance; next_page is set'), clarifying that cc selects both region and currency, and specifying that l accepts a locale such as en-US with the primary language used for text. This adds real operational meaning.

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?

Description uses a specific verb ('Browse') and resource ('PlayStation Store all-games grid'), and clearly states what is returned: per-item price, platforms, media, and filter facets with counts. This distinguishes it from sibling tools like playstation_search, playstation_category, and playstation_deals by focusing on the all-games grid specifically.

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?

The description implies usage: browse the all-games grid, pass page to advance, and use cc/l for region/language. However, it never explicitly says when to prefer this over playstation_search, playstation_category, or other PlayStation Store browsing tools, nor does it state any exclusions. The context is clear enough to infer, but not explicit.

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