Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gymshark_sitemap_urls

List Gymshark sitemap URLs by type—products, collections, pages, blogs, or all—and cap results with a limit. Return loc, handle, last modified, change frequency, and images.

Instructions

List Gymshark sitemap URLs. Lists URL entries from Gymshark's sitemaps, filtered by type (all by default, products, collections, pages, blogs, agentic_discovery or other) and capped by limit (default 50, max 250). Each has its loc, type, handle, last modified date, change frequency and any images.

Input 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

A3.7/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 usefully discloses the return fields (loc, type, handle, last modified, change frequency, images) in the absence of an output schema, plus the limit cap, but says nothing about auth needs, rate limits, or pagination behavior.

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?

Front-loaded with the core action and completed in three tight sentences. There is minor redundancy between 'List Gymshark sitemap URLs' and 'Lists URL entries from Gymshark's sitemaps', but nothing bloats the definition.

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 read tool with no output schema, the description sufficiently covers filtering, defaulting, capping, and the shape of each returned entry. Only pagination/auth behavior is unaddressed, which is a minor gap.

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%, so both parameters are already documented by the schema. The description restates the enum values and the default/max limit without adding syntax or semantic detail beyond what the schema 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?

States a specific verb+resource ('List Gymshark sitemap URLs') and clarifies it returns individual URL entries, distinguishing it from the sibling gymshark_sitemaps (which lists the sitemaps themselves). An agent can tell the two apart without opening either schema.

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 context is implied by the type filter and limit, and defaults are given, but there is no explicit when-to-use vs. the sibling gymshark_sitemaps tool and no statement of prerequisites or exclusions. Adequate but leaves routing to inference.

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