Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

usatoday_headlines

Fetch USA Today section headlines by section name, returning up to 100 items with titles, URLs, publish and update times, and lead images.

Instructions

Get USA Today section headlines. Returns the newest USA Today items for one top-level section, up to 100. section is required and takes news, sports, entertainment, life, money, tech, travel, opinion, cars, shopping, weather, politics or grocery. Each item has its title, URL, published and updated times, and lead image when there is one.

Input Schema

NameRequiredDescriptionDefault
sectionYesTop-level USA Today section

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 full burden and does a decent job: it discloses the return payload (title, URL, published and updated times, lead image when present), the freshness semantics ('newest'), and the hard cap of 100 items. It is silent on read-only/auth/rate-limit behavior, but the 'Get' phrasing and rich return description go well beyond bare structured fields.

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 with the core purpose in the first sentence, then scope, then return shape. It is efficient overall, though the inline re-listing of all thirteen enum values duplicates the schema and adds mild redundancy.

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 single-parameter, no-output-schema headlines tool, the description is largely complete: it explains what is fetched, how many items, and what each item contains, which compensates for the absent output schema. The remaining gap is sibling disambiguation against usatoday_news/usatoday_sections.

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 enum parameter is fully documented in the schema, so the schema already does the heavy lifting. The description restates the enum values and marks `section` as required, adding no syntax or format meaning beyond what is already structured.

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 states a specific verb and resource (get section headlines) and scopes it precisely: newest items for one top-level section, capped at 100. It does not, however, name or differentiate itself from close siblings like usatoday_news, usatoday_sections, or usatoday_article, leaving an agent to infer the boundary.

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?

Usage is implied rather than stated: 'for one top-level section' signals the retrieval context, but there is no explicit when-to-use/when-not or reference to alternative tools for the same content. The agent must infer that this is the browse-by-section entry point.

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