Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fashionphile_page

Fetch a Fashionphile static page by handle to get its title, URL, plain-text content, and created, updated, and published dates; unknown handles return 404.

Instructions

Get a Fashionphile static page. Returns one Fashionphile static page by its required handle, such as about: title, URL, plain-text content, and created, updated and published dates. An unknown handle returns 404. In a fallback mode flagged by transport_mode: "ssr_embedded", the response omits id.

Input Schema

NameRequiredDescriptionDefault
handleYesPage handle

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

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 burden and does add real behavioral context: it discloses the 404 response for an unknown handle and a fallback mode (transport_mode: 'ssr_embedded') that drops the `id` field. It omits auth or rate-limit notes, but the error and fallback disclosures are meaningful.

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 tight sentences with the core action front-loaded, then return fields, then edge cases. No filler; every sentence carries information.

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 convey return shape, which it does (title, URL, plain-text content, created/updated/published dates). Combined with the 404 and fallback-mode notes, an agent has enough to call it correctly for a simple get-by-handle tool.

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% ('Page handle'), so the schema already documents the single parameter. The description adds an example value (`about`) and confirms it is required, but no format or syntax beyond that. Baseline 3 is appropriate.

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+resource ('Get a Fashionphile static page') and emphasizes singularity ('Returns one'), which implicitly separates it from the plural fashionphile_pages list tool. However, it never names that sibling, so the differentiation is left to inference.

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 requirement of a `handle` and the singular return imply this is the fetch-one-page tool, but there is no explicit when-to-use guidance or exclusion relative to fashionphile_pages or other fashionphile siblings. Usage is only implied.

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