Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

chicagotribune_headlines

Fetch Chicago Tribune headlines for a chosen section slug, returning titles, article URLs, publication times, bylines, excerpts, and images so you can track coverage by topic.

Instructions

Get Chicago Tribune section headlines. Returns headlines from one Chicago Tribune section page. section is required and takes one of 60 slugs, such as local-news, crime-public-safety, chicago-bears, restaurants-food-drink or naperville-sun. Each story has a title, article URL, publication time, byline, excerpt and image where the card shows them. Most sections give about 10 stories.

Input Schema

NameRequiredDescriptionDefault
sectionYesChicago Tribune section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it discloses returned story fields, notes images are optional ("where the card shows them"), and gives an expected volume of about 10 stories. It does not explicitly describe read-only behavior, pagination, or invalid-slug handling, but the key output characteristics are covered.

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 front-loaded and appropriately sized, with no major digressions. There is slight redundancy between "section headlines" and "headlines from one ... section page," but it remains efficient.

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?

For a one-parameter headlines tool with no output schema and no annotations, the description gives enough detail about output fields, approximate story count, and section slug usage. It could be more complete by clarifying sibling choice and any pagination/error behavior, but nothing essential is missing for correct invocation.

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 enum already defines the valid section slugs, so the baseline is 3. The description reinforces that `section` is required and adds example slugs plus the count of 60, but it does not add substantial meaning beyond the schema.

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 Chicago Tribune section headlines") and clarifies it returns headlines from one section page. It is clear what the tool does, though it does not explicitly distinguish itself from nearby siblings like chicagotribune_news or chicagotribune_sections.

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 required `section` parameter and examples imply usage, but the description does not say when to choose this tool over chicagotribune_news, chicagotribune_sections, or article-specific siblings. No exclusions or alternative-selection guidance are provided.

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