Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gymshark_page

Fetch a Gymshark static page by handle to retrieve clean JSON with title, URL, plain-text content, and created, published, and updated times. Unknown handles return 404.

Instructions

Get a Gymshark static page. Returns one Gymshark static page by its handle, such as sports-bras: title, handle, URL, plain-text content, and created, published and updated times. Page HTML is not returned. An unknown handle returns a 404. id is absent when transport_mode is ssr_embedded.

Input Schema

NameRequiredDescriptionDefault
handleYesPage handle

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 solid work: it enumerates returned fields (title, handle, URL, plain-text content, created/published/updated times), states that page HTML is NOT returned, and defines the unknown-handle 404 behavior. It omits auth/rate-limit context and the transport_mode reference is cryptic, but the core behavioral profile is 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?

A single tight paragraph that front-loads purpose, then return fields, then error/special-case behavior. Every sentence carries information, though the trailing clause about `id` being absent under `transport_mode` is slightly cryptic since transport_mode is not a parameter here.

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 usefully explains the return shape itself, plus the 404 case and the ssr_embedded caveat. For a single-parameter read tool this is close to complete; only sibling routing and any auth/rate-limit notes are missing.

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% (handle: 'Page handle'), so the schema already documents the sole parameter and a baseline of 3 applies. The description adds a real example value and links the handle to 404 behavior, but no format or casing rules beyond that.

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 Gymshark static page') and immediately narrows it to a single page retrieved by handle, with a concrete example ('sports-bras'). This distinguishes it in spirit from the plural gymshark_pages sibling, but it never names or contrasts that sibling, so the differentiation is inferred rather than explicit.

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 usage ('returns one page by its handle') and notes the 404 failure mode for unknown handles, which helps an agent know when a call is valid. However, it offers no explicit when-to-use guidance or reference to alternatives such as gymshark_pages for listing or gymshark_sitemaps for discovery.

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