Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

thebodyshop_pages

List The Body Shop static pages in paginated JSON, 50 per request, with handle, title, URL, plain-text content and timestamps.

Instructions

List The Body Shop static pages. Lists The Body Shop static pages, 50 per request by default (limit up to 250), with page starting at 1. Each page has its handle, title, URL, plain-text content and timestamps. An empty result is a normal 200. 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.16.0

TDQS

A3.5/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 full burden. It does add genuinely useful behavior: default page size of 50, cap of 250, 1-based paging, and that an empty result is a normal 200 — but it omits permission/auth requirements and pagination termination hints beyond the empty-200 note.

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?

Efficient and front-loaded, though the first sentence duplicates the opening clause of the second ("List The Body Shop static pages" / "Lists The Body Shop static pages"), which is minor waste.

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, describing the returned fields (handle, title, URL, plain-text content, timestamps) is valuable, and the note that ssr_embedded mode degrades items to handle/url/updated_at prepares the agent for a thinner payload. Only auth/prerequisite context is missing.

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 `page` and `limit` are already fully documented. The description restates the default and ceiling for `limit` rather than adding new meaning, and the `transport_mode` reference describes a mode not present in the schema, which adds little for parameter interpretation.

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 ("List The Body Shop static pages") and the description makes clear this is the collection endpoint versus the singular thebodyshop_page sibling. It does not explicitly name the sibling, so differentiation relies on the reader inferring list vs. detail.

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 implied by "List" plus pagination semantics, but there is no explicit statement of when to use this versus thebodyshop_page or the collections/product siblings. An agent gets adequate but only inferential 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