Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

playstation_search

Search the PlayStation Store by term and get paginated results with prices, platforms, media, and classification. Use region and language options to refine results.

Instructions

Search the PlayStation Store. Returns a page of PlayStation Store search results (concepts and products) for a term, with pagination and per-item price, platforms, classification, and media. 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.

Input Schema

NameRequiredDescriptionDefault
lNoLanguage code
ccNoStore country code (ISO, selects currency)
pageNo1-based page number
termYesSearch term
page_sizeNoResults per page (max 48)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.14.0
    • addedInput schema / properties / page_size
      Added value: +{
+  "description": "Results per page (max 48)",
+  "type": "integer"
+}
  2. Addedv1.5.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it discloses pagination behavior, that next_page appears when more results exist, and what per-item fields are returned. It does not mention auth or rate limits, but for a read-only store search that is not a major omission.

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?

Three dense, well-structured sentences. Purpose and return shape are front-loaded, then pagination, then locale/region parameter behavior; there is no wasted text.

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 five-parameter search tool with no output schema and no annotations, the description gives enough context: result types, pagination, regional pricing, language behavior, and item-level fields. It stops short of full return-value detail, but is sufficient to call 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 baseline is 3. The description adds meaningful semantics beyond the schema for cc (selects region and price currency), l (accepts language code or locale and uses primary language for text), and page (used to advance pagination).

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 the PlayStation Store' and returns concepts/products for a term. It is clear what the tool does, but it does not differentiate itself from PlayStation siblings such as playstation_suggest, playstation_browse, or playstation_category.

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?

Provides no explicit when-to-use guidance or comparison to sibling tools. The agent can infer that it is for search, but the description never says when to choose this over playstation_suggest, playstation_browse, or playstation_category.

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