Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

brooklinen_pages

List Brooklinen static pages with pagination, returning handle, title, URL, content, and timestamps; for ssr_embedded transport, request each handle individually for content.

Instructions

List Brooklinen static pages. Lists Brooklinen static pages, limit per page (default 50, max 250) and page starting at 1. Each page has its handle, title, URL, plain-text content and timestamps. When transport_mode is ssr_embedded, items carry only handle, url and updated_at; request each handle singly for content.

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page, defaults to 1
limitNoMaximum static pages, defaults to 50 and supports up to 250

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A3.9/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden and does reasonably well: it discloses the returned fields (handle, title, URL, content, timestamps) and a mode-dependent degradation where only handle/url/updated_at are returned. It omits auth requirements, rate limits, and pagination termination behavior.

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?

Front-loaded with the core action and compact overall, but the opening two sentences redundantly repeat 'List(s) Brooklinen static pages', wasting one sentence on restatement before the pagination detail.

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 compensates by enumerating the returned fields and flagging the ssr_embedded caveat, enough for an agent to call and interpret results. The unexplained `transport_mode` reference (not a declared parameter) leaves a small gap in how that condition is triggered.

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%, and the description merely restates the same defaults (50, max 250, page starting at 1) already in the schema. Baseline 3 is appropriate since the schema does the heavy lifting and no additional format or interaction detail is added.

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: 'List Brooklinen static pages', with pagination scope. It distinguishes itself from the singular sibling by implying per-handle retrieval for content, though it never names `brooklinen_page` directly. Clear enough to route correctly, but sibling differentiation is only implicit.

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

Usage Guidelines4/5

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

Gives clear context: paginated listing with defaults and caps, plus the condition that under `transport_mode=ssr_embedded` the item content is absent and each handle must be requested singly. That conditional routing advice is genuinely useful, but the alternative tool is not named and no explicit 'when not to use' is stated.

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