Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

skims_sitemaps

List the child sitemap files in the SKIMS sitemap index to identify products, collections, pages, blogs, and other URLs before fetching each sitemap.

Instructions

List SKIMS sitemaps. Lists the child sitemaps in the SKIMS sitemap index, each with its loc URL and a type of products, collections, pages, blogs, agentic_discovery or other. Takes no parameters. Use it to see which sitemap files exist before listing their URLs.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the return shape (each child with a `loc` URL and a `type`), enumerates the type values (products, collections, pages, blogs, agentic_discovery, other), and states it takes no parameters, implying a safe read. It doesn't explicitly declare it read-only or note rate limits, but the behavioral picture is substantially clear.

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?

Three tight sentences: what it lists, what each item contains, and when to use it. Front-loaded with the core action and no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description steps in to describe the returned fields and type enum values, and it explains its role relative to URL listing. Nothing an agent needs in order to call this zero-parameter tool is missing.

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?

There are zero parameters, so the baseline is 4, and the description confirms this with 'Takes no parameters', removing any ambiguity about required inputs.

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 (List) and resource (SKIMS sitemaps), then explains exactly what is returned: child sitemaps from the SKIMS sitemap index. It is clearly distinguishable from the sibling skims_sitemap_urls, which lists URLs rather than the sitemap files themselves.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit context: 'Use it to see which sitemap files exist before listing their URLs', which positions it ahead of a URL-listing step. It implies the alternative without naming the exact sibling tool, so guidance is clear but not fully explicit about the alternative's name.

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