Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

everlane_page

Fetch an Everlane 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 Everlane static page. Returns one Everlane static page by its required handle: 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.16.0

TDQS

A3.8/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 disclose real behavioral traits: the returned fields (title, URL, content, dates), a 404 on unknown handle, and a fallback transport_mode that omits `id`. It omits auth/permission or caching notes, but the error and edge-case disclosure is strong.

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, front-loaded with the action and resource, followed by return shape and edge cases. Nothing extraneous; every clause earns its place (minor grammar slip 'a Everlane' aside).

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?

For a one-parameter read tool with no output schema, the description usefully enumerates return fields, documents the 404 path, and flags the ssr_embedded variant that drops `id`. Adequate for correct invocation, though an explicit pointer to everlane_pages would round it out.

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 parameter is already documented as 'Page handle'. The description restates that handle is required but adds no format or syntax detail beyond the schema, so the baseline of 3 applies.

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 ('Get') and resource ('Everlane static page') fetched by a required handle, so the agent knows it is a single-resource lookup. It does not explicitly name or contrast with the sibling everlane_pages, but the singular scope is clear from the text.

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 the usage ('by its required `handle`') but offers no explicit when-to-use guidance, prerequisites, or routing to the sibling everlane_pages for listing pages. Usage must be inferred from the schema's required handle.

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