Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

wapo_headlines

Retrieve Washington Post headlines for a specified section, returning each story's title, URL, description, publication time, and lead image in structured JSON.

Instructions

Get the latest stories in a Washington Post section. Returns the first page of a Washington Post section front: each story's title, canonical URL, description, section, publication time, and lead image. Section must be a path returned by /wapo/sections.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionYesSection path from /wapo/sections

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4/5.0
Behavior3/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 of disclosure. It discloses the output shape (each story's title, URL, description, section, publication time, and lead image) and hints at pagination by specifying 'first page', but does not explain how to retrieve subsequent pages or note any rate limits.

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 tight sentences with zero waste. The action is front-loaded, followed by the return-value contract, then the input prerequisite. Every sentence earns its place.

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?

Since there is no output schema, the description takes responsibility for explaining return values and enumerates them explicitly. Together with the input-source prerequisite and the pagination hint, it covers what an agent needs to call this one-parameter tool correctly.

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%: the 'section' parameter is already fully documented as 'Section path from /wapo/sections'. The description reinforces this dependency by repeating the constraint, adding marginal value beyond what the schema provides, so baseline 3 is appropriate.

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'), a specific resource ('latest stories in a Washington Post section'), and clear scope ('first page of a Washington Post section front'). It cleanly differentiates from siblings like wapo_article (full article content), wapo_author, and wapo_sections by being the section-front listing tool.

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 usage prerequisite: the 'section' must be a path returned by /wapo/sections, which tells the agent how to obtain a valid input. It establishes clear context for when this tool applies (listing section-front stories) though it does not explicitly name alternative tools for adjacent tasks like fetching full articles.

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