Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

brooklinen_page

Fetch a Brooklinen static page by handle to get its title, URL, plain-text content, and created/published/updated times; invalid handles return 404.

Instructions

Get a Brooklinen static page. Returns one Brooklinen static page by its handle: id, title, URL, plain-text content, and created, published and updated times. A missing handle returns 404. When transport_mode is ssr_embedded, the content is plain text from the page's rich-text blocks and id is omitted.

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 meaningful work: it specifies the 404 error behavior for a missing handle and discloses a mode-dependent return shape (`transport_mode=ssr_embedded` yields plain text from rich-text blocks and omits `id`). It still doesn't cover caching, auth, or rate limits, but the error and mode-shape disclosures are the important behavioral traits here.

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 front-loaded sentences with no filler: what it returns, then the error case, then the mode-specific nuance. The final sentence is somewhat dangling since `transport_mode` does not appear in the schema, but every sentence conveys real 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?

For a single-parameter retrieval tool with no output schema, the description covers the return fields, the failure mode (404), and a transport-dependent variation. The only gap is the unexplained `transport_mode` reference, which is not present in the documented input schema.

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 there is a single parameter, so the schema already documents `handle`; the description adds only the 404 consequence of a bad handle. The mention of `transport_mode` is not a declared parameter in the input schema, which introduces mild confusion rather than useful parameter detail.

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 Brooklinen static page") and enumerates the returned fields (id, title, URL, content, timestamps), which clearly distinguishes it from the list-style sibling `brooklinen_pages`. It does not explicitly name that sibling or contrast itself with it, so an agent must infer the singular-vs-list split.

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 handle-based retrieval model implies when to use it (you have a page handle and want that page), and the 404 note tells the agent what happens on a bad handle. However, there is no explicit "use brooklinen_pages to list or discover handles" routing, so the choice among siblings is left 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