Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

denverpost_headlines

Fetch current Denver Post headlines for one section or topic archive using a required section slug; returns article titles, URLs, summaries, authors, times, and images when available.

Instructions

Get Denver Post section headlines. Returns current headlines for one Denver Post section or topic archive. section is required and must be a slug from the sections endpoint, such as business, denver-broncos, colorado or weather; an invalid value returns an invalid-params error. Items carry title and URL, plus summary, author, publication time and image when the card shows them. Cards without a dated Denver Post article URL are skipped.

Input Schema

NameRequiredDescriptionDefault
sectionYesSection or topic slug returned by denverpost-sections

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.9/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 delivers real behavioral detail: invalid section values return an invalid-params error, and cards without a dated Denver Post article URL are silently skipped. It also enumerates the returned fields. It omits auth/rate-limit context, but discloses the non-obvious filtering behavior.

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?

Front-loaded and well organized: purpose, then scope, then parameter constraint, then return shape. The first two sentences overlap slightly ('Get ... headlines' vs 'Returns current headlines'), but overall it is tight and each remaining sentence adds value.

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?

With no output schema, the description steps in to describe the return shape (title, URL, optional summary/author/publication time/image) and the skip rule for undated cards. For a single-parameter, enum-constrained read tool this is complete enough to call correctly.

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 already 100% with an enum, setting a baseline of 3. The description goes beyond the schema by stating the value must be a slug from the sections endpoint, giving concrete examples (business, denver-broncos, colorado, weather), and describing the error on invalid input.

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?

States a specific verb and resource ('Get Denver Post section headlines') and clarifies it returns 'current headlines for one Denver Post section or topic archive.' It does not explicitly contrast with the sibling tools denverpost_news or denverpost_article, so sibling differentiation is left to inference.

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?

It implies usage (fetch headlines for a given section) and specifies that `section` must come from the sections endpoint, which is a useful prerequisite. However, it gives no explicit when-to-use/when-not guidance against the nearby denverpost_news or denverpost_article tools.

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