Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

psastore_collections

Retrieve PSA Store collections with pagination. Returns normalized collection data from the PSA Team Store, supporting page and limit parameters for efficient listing.

Instructions

List PSA Store collections. Returns normalized collections from the PSA Team Store (https://store.psacard.com). The storefront URL is fixed server-side. Valid empty result pages return 200 with an empty collections array.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page, defaults to 1
limitNoMaximum collections, defaults to 50 and supports up to 250

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden. It discloses that collections are normalized, the storefront URL is fixed server-side, and empty result pages return 200 with an empty array. This adds useful context beyond the schema, though it stops short of describing response structure or rate limits.

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 sentences with no filler. The purpose is front-loaded and every sentence adds information: what is listed, where it comes from, and an important edge-case behavior.

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 simple list tool with two optional parameters and no output schema, the description is largely complete. It covers the source, normalization, fixed URL, and empty-result behavior. It does not detail the collection object fields, but the name 'collections' and the array mention provide sufficient guidance for basic invocation.

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 description coverage is 100%, so the parameters are already documented. The description adds no extra meaning about page or limit semantics, so the baseline of 3 applies.

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 clearly states the tool lists PSA Store collections, which is a specific verb and resource. It does not explicitly differentiate from sibling tools like psastore_collection_products, but the resource name and normalization note make the purpose reasonably distinct.

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 (call when you need store collections) but provides no explicit when-to-use or when-not-to-use guidance. It does not mention alternatives such as psastore_collection_products or psastore_products, leaving the selection decision to inference.

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