Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kyliecosmetics_pages

List Kylie Cosmetics static pages with page and limit controls, returning handles, titles, URLs, content, and timestamps.

Instructions

List Kylie Cosmetics static pages. Lists static pages from the Kylie Cosmetics store, paged with page (default 1) and limit (default 50, max 250). Each page has its id, handle, title, URL, plain-text content and timestamps. When transport_mode is ssr_embedded, items carry only handle, url and updated_at.

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page, defaults to 1
limitNoMaximum static pages, defaults to 50 and supports up to 250

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A3.7/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 meaningful work: it enumerates returned fields (id, handle, title, URL, content, timestamps) and discloses a conditional output shape under ssr_embedded. It does not cover permissions, error behavior, or why transport_mode appears despite not being a schema parameter, which is mildly confusing.

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?

Three compact sentences, front-loaded with the scoping statement. The second sentence ('Lists static pages from the Kylie Cosmetics store') is largely redundant with the first, a minor waste.

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?

No output schema exists, so the description must describe return values and it does list the item fields. Parameters are fully covered by the schema, so the only gap is the ungovernable transport_mode variant and the absence of any error/limit caveats.

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% and both parameters are already documented there; the description merely restates the same defaults (page=1, limit=50/250). It adds no syntax, ordering, or edge-case meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'List Kylie Cosmetics static pages.' It is clearly distinguishable from generic sibling names, though it never explicitly contrasts with the singular kyliecosmetics_page detail tool. Clear but without explicit sibling differentiation.

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 is only implied by the verb 'list' plus pagination defaults. There is no statement of when to use this versus kyliecosmetics_page (single page), kyliecosmetics_sitemaps, or kyliecosmetics_store. 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