Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kyliecosmetics_page

Fetch a Kylie Cosmetics static page by handle to get its ID, title, URL, plain-text content, and timestamps; unknown handles return 404.

Instructions

Get a Kylie Cosmetics static page. Returns one static page from the Kylie Cosmetics store by handle. The response has the page id, title, URL, handle, plain-text content, and created, updated and published times. Content is text, not HTML. In some cases transport_mode is ssr_embedded and id is omitted. An unknown handle returns 404.

Input Schema

NameRequiredDescriptionDefault
handleYesPage handle

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A3.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 enumerates the returned fields, warns that content is plain text rather than HTML, notes the `ssr_embedded` transport mode where `id` is omitted, and states that an unknown handle yields 404. Missing auth/permission notes, but the error and output behavior are unusually well disclosed.

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?

Four tight sentences, front-loaded with the purpose, then return shape, then edge cases. Everything earns its place, though the transport_mode detail could be trimmed for non-consumers.

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?

With no output schema, the description must explain the return value and does so (id, title, URL, handle, content, timestamps) plus the content-format caveat and 404 behavior. Only gaps are permissions and any guidance on sourcing the handle from the sitemap/page siblings.

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 coverage is 100% and the single `handle` parameter is already documented as 'Page handle'. The description adds only marginal value by implying the handle is the lookup key for one static page, which is the baseline expectation when the schema does the heavy lifting.

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?

States a specific verb and resource ('Get a Kylie Cosmetics static page') and the lookup key ('by `handle`'). It is distinguishable from siblings like kyliecosmetics_pages and kyliecosmetics_product, though it never names the plural page-list sibling as a contrast.

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

Usage Guidelines2/5

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

No indication of when to call this versus kyliecosmetics_pages, kyliecosmetics_store, or the sitemap tools. Usage is only implied by the required `handle` argument; there are no explicit conditions or alternatives.

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