Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ohpolly_pages

List Oh Polly static pages with pagination, returning handle, title, URL, content, and timestamps. Some responses omit content, so fetch a single page for details.

Instructions

List Oh Polly static pages. Lists Oh Polly's static pages, paged with page (default 1) and limit (default 50, max 250). Each page has its handle, title, URL, plain-text content and timestamps. In some responses transport_mode is ssr_embedded and items carry only handle, url and updated_at, so fetch a single page for its 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?

With no annotations, the description carries the full burden and discloses pagination defaults, returned fields (handle, title, URL, plain-text content, timestamps), and an important edge case about reduced fields in ssr_embedded responses. It does not cover auth, rate limits, or error behavior, but for a read-only list tool this is substantial.

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 purpose and efficient overall, though the first sentence 'List Oh Polly static pages.' is essentially restated by the second sentence 'Lists Oh Polly's static pages, paged...', creating minor redundancy.

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?

Given a simple list tool with no annotations and no output schema, the description covers pagination, returned fields, and an important edge case. It is close to fully sufficient for an agent to call correctly, missing only minor details like total count or error conditions.

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%, so both parameters are already documented in the schema. The description repeats the defaults and max value for page and limit but adds no new syntax or format guidance beyond what the schema provides; baseline 3 is appropriate.

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 Oh Polly static pages') and implicitly distinguishes scope by mentioning fetching a single page for content. However, it does not name the sibling tool (ohpolly_page) explicitly, so it falls short of full sibling differentiation.

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?

Provides a clear condition for when to prefer the single-page alternative: 'In some responses transport_mode is ssr_embedded... so fetch a single page for its content.' It does not explicitly name that alternative tool or state when not to use this tool, but the context is clear.

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