Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

pagesix_headlines

Fetch recent Page Six headlines by section slug. Returns story titles, URLs, and optional summaries, authors, or images.

Instructions

Get Page Six section headlines. Returns recent Page Six stories for one section. section is required and takes one of 30 slugs, such as celebrity-news, royal-family, taylor-swift or new-york-city-society. Each item has a title and URL, and may include summary, author, publication time and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesPage Six RSS section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the burden. It usefully discloses the return shape (title and URL always, plus optional summary, author, publication time and image), which goes beyond what the schema provides. However it omits result count/pagination and read-only framing beyond the implicit "Get".

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?

Three short sentences, front-loaded with purpose followed by the parameter constraint and return shape. No wasted filler, though the example slug list is mild redundancy against the enum.

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 appropriately explains the item contents, and with a single required enum parameter the definition is nearly self-contained. Only pagination/result-count detail is missing.

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 coverage is 100% and the enum already enumerates all 30 slugs, so the parameter is fully documented structurally. The description's four example slugs merely illustrate the enum, adding little beyond the schema, so the baseline 3 applies.

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+resource ("Get Page Six section headlines") and scope ("for one section"). An agent can distinguish it from siblings like pagesix_sections, pagesix_news, and pagesix_article without opening any 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?

Implies usage by stating that a section is required, but never explicitly says when to choose this over pagesix_sections or pagesix_news, nor does it exclude any case. The guidance is inferable but not 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