Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

thebodyshop_pages

Retrieve paginated static pages from The Body Shop storefront as normalized data. Use page and limit inputs to collect structured page listings for crawling or analysis.

Instructions

List The Body Shop static pages. Returns normalized static pages from The Body Shop (https://www.thebodyshop.com). The storefront URL is fixed server-side.

Input Schema

TableJSON 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.16.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It adds useful context that output is 'normalized' and that the storefront URL is fixed server-side, implying no per-request URL control. However, it doesn't disclose auth needs, rate limits, or explicitly confirm read-only behavior, though for a list tool that is reasonably inferred.

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?

Two sentences with no wasted words. The action and resource are front-loaded, followed by useful normalization and fixed-URL context. Every sentence contributes meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a low-complexity list tool with two optional parameters. It tells the agent what it returns and the source, but it doesn't define what 'static pages' includes or what the normalized return representation looks like, and there is no output schema to fill that gap. Usable, but with some ambiguity.

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%, with both page and limit fully documented in the input schema. The description adds no new parameter-level detail, but it does explain why no URL parameter exists ('storefront URL is fixed server-side'). This meets the baseline without exceeding it.

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 states a specific verb and resource: 'List The Body Shop static pages.' The 'static pages' qualifier helps distinguish it from product and collection tools, and the source URL adds clarity. It doesn't explicitly differentiate from the sibling thebodyshop_page, but the plural 'pages' and list framing make the purpose clear.

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?

There is no guidance on when to use this tool versus alternatives like thebodyshop_page, thebodyshop_sitemaps, or other 'pages' tools in the sibling set. The description only says what it does, not the conditions that would make it the right choice, nor any exclusions or fallbacks.

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