Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

thebodyshop_sitemap_urls

Retrieve capped The Body Shop sitemap URLs by type (products, collections, pages, blogs, and more) with an optional limit, returning clean entries from fixed storefront child sitemaps.

Instructions

List The Body Shop sitemap URLs. Returns capped URL entries from The Body Shop's (https://www.thebodyshop.com) child sitemaps matching the requested type. The storefront URL is fixed server-side.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoSitemap type. Allowed values: all, products, collections, pages, blogs, agentic_discovery, other
limitNoMaximum URL entries, defaults to 50 and supports up to 250

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / type / enum
      Added value: +[
+  "all",
+  "products",
+  "collections",
+  "pages",
+  "blogs",
+  "agentic_discovery",
+  "other"
+]
  2. Addedv1.16.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses that results are capped, that only child sitemaps are considered, and that the storefront URL is fixed server-side. It does not explicitly state read-only semantics (though 'List' implies it) or error response behavior, but the capped and fixed-URL traits are useful and add transparency.

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 efficient sentences with no filler. The first sentence states the core purpose; the second adds the key constraints (capped, child sitemaps, fixed URL). Everything earns its place.

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?

The tool is simple with two parameters and no output schema. The description covers purpose, cap, child-sitemap scope, and fixed URL. It doesn't describe the return format, but the name implies URLs, and an agent can infer acceptable inputs from the schema. Minor gap: no mention of what 'agentic_discovery' type means, but that's in the enum.

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% for both parameters: 'type' has an enum with descriptions, and 'limit' has default/max info. The description adds no extra semantic value beyond what the schema already provides, so the baseline 3 applies.

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 clearly states the verb 'List' and the resource 'The Body Shop sitemap URLs', and specifies that it returns entries from child sitemaps of the given domain. This differentiates it from other sitemap-related tools (like thebodyshop_sitemaps) by clarifying it returns URLs, not sitemap metadata.

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?

The description implies usage ('matching the requested type') but does not explicitly name alternatives or when not to use this tool. Given the sibling tool 'thebodyshop_sitemaps' likely provides different functionality (e.g., list of sitemap files), an agent could benefit from explicit routing. No guidance on exclusion or alternative selection is provided.

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