Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fashionphile_sitemaps

List Fashionphile sitemap index entries to retrieve each child sitemap URL and inferred type, such as products, collections, pages, blogs, or agentic discovery.

Instructions

List Fashionphile sitemaps. Lists the child sitemaps in Fashionphile's sitemap index, with no parameters. Each entry has its loc URL and an inferred type: products, collections, pages, blogs, agentic_discovery or other. Product sitemap URLs may carry from and to query values.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and usefully discloses that there are no parameters, the returned entry fields (`loc` and inferred `type`), the possible type classifications, and that product sitemap URLs may include `from`/`to` query values. It does not explicitly state read-only status, but 'List' and the output detail make the non-mutating behavior clear enough.

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?

The description is short and front-loaded, with the core purpose stated first. However, the opening 'List Fashionphile sitemaps' is partially repeated by the next sentence 'Lists the child sitemaps...', creating minor redundancy.

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?

Given zero parameters, no annotations, and no output schema, the description supplies enough for an agent to call and interpret the result: it explains the return fields, the inferred type taxonomy, and the query-value note. It could be slightly more complete by mentioning ordering or whether all child sitemaps are always returned, but those are minor omissions for this low-complexity tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

This tool has zero parameters, so the baseline is 4. The description adds a small amount of value by explicitly stating 'with no parameters', but there are no parameter semantics to clarify beyond that.

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 ('Fashionphile sitemaps') and clarifies that it returns child sitemaps in the sitemap index. This distinguishes it from URL-level sitemap tools such as fashionphile_sitemap_urls.

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 it is used to discover child sitemaps before fetching their URLs, but it never explicitly states when to choose this tool over fashionphile_sitemap_urls or other sitemap-related siblings. No exclusions or alternative guidance are 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