Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

thebodyshop_collections

Retrieve The Body Shop product collections with pagination. Specify page and limit to fetch clean JSON collection data for browsing or catalog tasks.

Instructions

List The Body Shop collections. Returns collections from The Body Shop (https://www.thebodyshop.com). The storefront URL is fixed. Valid empty result pages return 200 with an empty collections array.

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

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden but only partly discharges it. It does add real behavioral context: the storefront URL is fixed and empty pages return 200 with an empty array, which is genuinely useful for an agent parsing results. It says nothing about auth, rate limits, or pagination range beyond the schema defaults.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

It is front-loaded with the core action, but the first two sentences are redundant: "List The Body Shop collections" is immediately restated as "Returns collections from The Body Shop." The empty-page note is a distinct, useful sentence.

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 2-param, read-only list tool with no output schema, the description covers the essentials and the empty-result edge case, which is the main ambiguity an agent would face. Missing only sibling routing guidance, which is covered under usage.

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 both parameters (page, limit) are already documented with defaults and the 250 cap. The description adds no syntax or semantic detail beyond the schema, so the baseline 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 gives a specific verb and resource ("List The Body Shop collections") and scopes it to a fixed storefront. It implicitly contrasts with product-oriented siblings, but never names them or explicitly distinguishes this from thebodyshop_collection_products.

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 explicit when-to-use or when-not-to-use guidance. "The storefront URL is fixed" is a constraint, not usage direction, and the obvious alternative (thebodyshop_collection_products) is not referenced.

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