Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

houston_chronicle_headlines

Fetch Houston Chronicle section headlines by slug; if Hearst's Client Challenge appears, requests are retried through rendering backends without bypassing access controls.

Instructions

Get Houston Chronicle section headlines. Returns current public headlines from a verified Houston Chronicle editorial section. Pages that return Hearst's Client Challenge are retried through configured rendering backends; the service does not solve or bypass access controls.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionYesHouston Chronicle public section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses retry behavior for Hearst Client Challenge pages and clarifies that it does not bypass access controls, which is meaningful operational context. However, it says nothing about return shape (e.g., list of headline items), item counts, or freshness/update cadence.

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?

The description is three compact sentences with the core purpose front-loaded. The final sentence about Client Challenge retries earns its place by conveying real behavior, though it sits slightly apart from the headline-fetching purpose.

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

Completeness3/5

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

For a single-parameter headlines tool with no output schema, the definition covers purpose and a key reliability behavior, but leaves the return structure and volume unspecified. It is adequate but does not fully close the loop on what the agent receives.

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% and the single 'section' parameter is fully enumerated with a documented slug, so the schema already does the heavy lifting. The description adds no syntax, default, or format detail beyond what the enum provides, which warrants the baseline 3.

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?

The description opens with a specific verb and resource ('Get Houston Chronicle section headlines'), which clearly identifies the operation. It distinguishes itself from the sibling 'houston_chronicle_article' by targeting headlines rather than full articles, though it does not explicitly name 'houston_chronicle_news' or 'houston_chronicle_sections' as alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance or when-not-to-use guidance. The mention of 'section headlines' implies the agent should supply a section slug, but nothing routes the agent between this tool and the closely named siblings like houston_chronicle_news or houston_chronicle_article.

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