Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

playstation_page

Retrieve a PlayStation Store merchandising page by alias to get its shelves and curated collection links, including category_id values for fetching full collection grids.

Instructions

Get a PlayStation Store merchandising page by alias. Reads any PlayStation Store merchandising page by alias (e.g. collections, subscriptions, or a promotional alias) and returns its shelves (sections) plus the curated collection links found on the page. Each collection link carries a category_id (UUID) you can pass to /playstation/category to fetch that collection's full, paginated title grid. Known aliases: collections, subscriptions, deals, latest. 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.

Input Schema

NameRequiredDescriptionDefault
lNoLanguage code
ccNoStore country code (ISO, selects currency)
aliasYesMerchandising page alias

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose meaningful behavior: it is a read of a merchandising page and it returns shelves plus curated collection links carrying category_id UUIDs. It does not explicitly confirm read-only status or mention any auth/rate-limit constraints, but the read semantics are clear from the wording.

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 action and efficiently organized, with the alias list and param notes at the end. The opening two sentences restate the same verb/resource ('Get... by alias' then 'Reads any... by alias'), a small redundancy that keeps it just short of fully tight.

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?

No output schema exists, so the description must explain the return, and it does: shelves (sections) plus curated collection links with a category_id that chains to playstation_category. Combined with the alias examples and region/language semantics, an agent has everything needed to call it and use the result.

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 baseline is 3, and the description goes beyond the schema: it explains cc selects store region and price currency, that l accepts a language code or locale (en, en-US) with the locale's primary language used for text, and it enumerates known alias values. This adds real meaning over the terse schema 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?

States a specific verb and resource (get/read a PlayStation Store merchandising page) scoped by alias, and names the concrete return shape (shelves plus curated collection links). It also distinguishes itself from the sibling playstation_category by explaining that this tool surfaces the category_id links you then feed to that tool.

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

Usage Guidelines4/5

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

Clear context for use: fetch a merchandising page to get its shelves and curated collection links, then pass each link's category_id to /playstation/category for the full paginated title grid. The known aliases (collections, subscriptions, deals, latest) further constrain when it applies. No explicit when-not guidance is given, but the sibling hand-off is well stated.

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