Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

psastore_pages

List static pages from the PSA Team Store with page and limit controls, returning handle, title, URL, content, and timestamps for browsing, audits, or syncs.

Instructions

List PSA Store static pages. Lists static pages from the PSA Team Store, 50 per page by default (limit up to 250, page starts at 1). Each page has its handle, title, url, plain-text content and timestamps. When transport_mode is ssr_embedded, items carry only handle, url and updated_at.

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page, defaults to 1
limitNoMaximum static pages, defaults to 50 and supports up to 250

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.9/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, and it does real work: it states the default page size, the 250 ceiling, the 1-based paging model, the returned field set, and a mode-dependent caveat (`ssr_embedded` returns only handle/url/updated_at). That conditional payload-shape note is genuinely useful context. It does not cover auth/rate-limit behavior, which keeps it from a 5.

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?

Three sentences, front-loaded with the core purpose and with the paging constraints placed before the payload-shape caveat. Minor redundancy: "Lists static pages from the PSA Team Store" largely restates the opening clause, costing a small amount of surface area.

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?

With no output schema and no annotations, the description thoughtfully supplies the return fields, pagination behavior, and the reduced-field mode. That is enough for an agent to call it correctly. It stops short of explaining what pagination metadata comes back or how to know when the list is exhausted, and the unexplained `transport_mode` reference leaves a loose end.

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%, and the schema already states the default of 1, the default of 50, and the 250 cap, so the description mostly restates structured data. It adds no format or interaction nuance beyond that baseline. Notably it references a `transport_mode` input that does not appear in the schema at all, which is unhelpful for parameter interpretation.

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 opens with a specific verb+resource ("List PSA Store static pages") and immediately reinforces it with the scope ("static pages from the PSA Team Store"). This clearly separates it from the singular `psastore_page` detail sibling, and no schema needs to be opened to know what it retrieves.

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?

Usage is only implied: the word "List" combined with pagination defaults signals this is the collection/browse tool, but the description never says when to use it over `psastore_page`, `psastore_search_suggest`, or `psastore_sitemap_urls`. No prerequisites, exclusions, or alternatives are 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