Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ohpolly_page

Fetch an Oh Polly static page by handle to get its title, URL, cleaned plain-text content, and created, published, and updated timestamps; unknown handles return 404.

Instructions

Get a Oh Polly static page. Returns one Oh Polly static page by its handle: title, page URL, plain-text content, and created, published and updated times. Content is cleaned text, not HTML. An unknown handle returns 404. The store is fixed to Oh Polly, so no store URL is needed. Some responses include transport_mode set to ssr_embedded and omit 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 well: it discloses the returned fields (title, URL, cleaned text content, timestamps), that content is plain text not HTML, that an unknown handle yields 404, that the store is fixed, and even a response quirk (transport_mode ssr_embedded, missing id). It omits auth/rate-limit context but is otherwise unusually rich.

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?

The core purpose is front-loaded in the first sentence, and every subsequent sentence adds a distinct fact (return shape, content type, 404 behavior, fixed store, response quirk). Only mild redundancy around the 'Oh Polly static page' repetition.

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 steps in to describe the return payload and error behavior, and it flags the fixed-store and transport_mode caveats. It is complete enough to call correctly, missing only explicit sibling routing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (the handle param is documented), giving a 3 baseline. The description adds genuine value beyond the schema by explaining the handle is the page identifier and that an unknown value returns 404, which the schema does not say.

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 (Oh Polly static page) and the retrieval key (handle), so an agent knows exactly what it returns. It does not, however, distinguish itself from the plural sibling ohpolly_pages (list) or ohpolly_pages variants, leaving that differentiation 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 'by its handle' framing implicitly tells the agent this is the single-page lookup, but there is no explicit when-to-use, when-not, or reference to the ohpolly_pages alternative for listing. Usage is implied rather than 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