Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

skims_page

Retrieve a SKIMS static page by handle, returning its title, URL, cleaned plain-text content, and timestamps; unknown handles return 404.

Instructions

Get a SKIMS static page. Returns one SKIMS static page by its handle: id, title, URL, plain-text content and the created, published and updated timestamps. Page text is cleaned, not raw HTML. An unknown handle returns 404. When the reduced form is served, transport_mode is ssr_embedded and id is omitted.

Input Schema

NameRequiredDescriptionDefault
handleYesPage handle

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A4/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 cleaned-plain-text content format (not raw HTML), the 404 on unknown handle, and the reduced `ssr_embedded` transport variant where `id` is omitted. It doesn't cover auth or rate limits, but the error and transport behavior is above average for an unannotated tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action and resource, then return fields, then format and edge-case behavior. Every sentence adds distinct information with no 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?

There is no output schema, so the description correctly enumerates the returned fields (id, title, URL, content, timestamps) and the error behavior, which is enough to call it correctly. Missing only permission/availability context, a minor gap.

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% for the single `handle` param, so the schema already documents it. The description only restates 'by its handle' and adds no format or syntax guidance beyond that, making 3 the correct baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Get) and resource (SKIMS static page) and pins the lookup key (`handle`). An agent can distinguish this from the sibling `skims_pages` (which lists pages) without opening either schema.

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 mechanism ('by its `handle`') is clear, which implies usage, but the description never states when to prefer this over `skims_pages` or any other SKIMS tool, and offers no exclusions. Usage is implied rather than guided.

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