Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ohpolly_sitemap_urls

Retrieve capped Oh Polly child sitemap URLs by type—products, collections, pages, blogs, or all—for crawling, indexing, or link analysis.

Instructions

List Oh Polly sitemap URLs. Returns capped URL entries from Oh Polly's (https://www.ohpolly.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

A3.8/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses that results are 'capped' and that 'the storefront URL is fixed server-side', which are useful behavioral details. However, it does not mention potential rate limiting, pagination, or what happens when no type is specified, leaving some gaps.

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?

The description is two sentences, front-loaded with the primary action and then adding context about the fixed URL. Every word earns its place – no filler, no repetition of schema details. Exemplary structure.

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 sitemap fetch tool with optional parameters and no output schema, the description is nearly complete. It states what it returns, the fixed domain, and the notion of capping. Missing only explicit default behavior for the optional 'type' parameter (e.g., what if omitted?), but that's a minor gap given the schema already covers defaults.

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% – both 'type' and 'limit' have descriptions that cover their allowed values and defaults. The description adds 'matching the requested type' which reinforces param purpose but doesn't provide additional semantics beyond the schema. Baseline 3 is appropriate.

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 uses a specific verb ('List') and resource ('Oh Polly sitemap URLs'), explicitly stating it returns 'capped URL entries from Oh Polly's child sitemaps'. This clearly differentiates from the sibling 'ohpolly_sitemaps' which lists sitemap files themselves, not the URLs within them.

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 this tool is for fetching URLs of a specific type (products, collections, etc.) from sitemaps, but does not explicitly state when to use this over alternatives like ohpolly_products or ohpolly_collections. It lacks explicit when/when-not guidance and doesn't name alternative tools.

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