Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

pagesix_article

Fetch structured Page Six article content from a canonical URL, including title, authors, images, timestamps, paywall status, and body paragraphs.

Instructions

Get Page Six article content. Returns a Page Six article by canonical url in the form https://pagesix.com/YYYY/MM/DD/<section>/<slug>/: title, description, section, authors, lead image, publication and update times, a paywalled flag and the body paragraphs.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Page Six article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/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 it does disclose the return shape (title, description, section, authors, lead image, times, body paragraphs) plus a `paywalled` flag that materially affects how an agent should treat the content. It omits error/auth behavior, but the disclosure is solid for a read-only fetch.

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?

Two sentences, front-loaded with the purpose, then the return contract. No filler and nothing redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with no output schema, the description supplies the URL format and enumerates returned fields, so an agent has everything needed to invoke it and interpret the response.

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% and only one parameter exists, so the baseline is 3, but the description goes further by specifying the exact canonical URL pattern `https://pagesix.com/YYYY/MM/DD/<section>/<slug>/`, giving the agent concrete format guidance beyond the schema's generic 'Canonical Page Six article URL'.

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 (Page Six article content) and makes clear it retrieves a single article by canonical URL, which cleanly separates it from the sibling pagesix_headlines, pagesix_news, and pagesix_sections list tools.

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 URL form implies the tool is for fetching one already-known article, but it never states when to use this versus pagesix_headlines/news/sections or what happens with a non-canonical URL. Usage is inferable rather than explicit.

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