Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rebag_pages

List Rebag storefront static pages with pagination, returning each page's handle, title, URL, plain-text content, and dates.

Instructions

List Rebag static pages. Lists the static pages on Rebag's storefront, paged with page (from 1) and limit (default 50, max 250). Each entry has handle, title, url, plain-text content and its dates. An empty page of results returns an empty pages array. In ssr_embedded mode only handle, url and updated_at are filled.

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

A4.1/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 burden and does well: it discloses pagination defaults, that an empty page returns an empty `pages` array, and that `ssr_embedded` mode degrades the payload to only `handle`, `url` and `updated_at`. It stops short of mentioning auth needs or rate limits, so not 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four tight sentences, front-loaded with the action and scope, then pagination, then return shape, then the mode caveat. No filler.

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?

With no output schema, the description still enumerates the returned fields (`handle`, `title`, `url`, `content`, dates) and explains the empty-result and ssr_embedded cases, so an agent knows what to expect without inspecting a schema.

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 coverage is 100%, so the schema already documents `page` (1-based, default 1) and `limit` (default 50, max 250). The description restates the same facts without adding format or edge-case meaning, which is the baseline-3 case.

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 ('List') and resource ('Rebag static pages') and immediately scopes it to the storefront's static pages, which cleanly separates it from the singular rebag_page sibling and from rebag_products/collections.

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 by the plural resource name; the description never says when to use this list endpoint versus the singular rebag_page detail tool, nor does it name any alternative. It gives operational context (pagination) but no routing guidance.

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