Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

latimes_headlines

Fetch Los Angeles Times section headlines with titles, URLs, summaries, authors, publication times, and lead images; choose any section or default to main.

Instructions

Get Los Angeles Times section headlines. Returns fresh headlines from a public Los Angeles Times section RSS feed: title, canonical URL, summary, author, publication time, and lead image. section defaults to main.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionNoSection slug from latimes-sections, defaults to main

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden; it discloses that the data comes from a public RSS feed, that headlines are 'fresh', and enumerates the exact returned fields. It does not cover limits, ordering, pagination, or failure modes, but for a simple feed fetch this is reasonable context.

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 sentences with no filler; the purpose and return fields are front-loaded, and the default is stated at the end. Every sentence conveys necessary calling information.

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-optional-parameter headline fetcher without an output schema, the field list and section enum are nearly sufficient. Missing details are minor (e.g., count/order of headlines and the precise freshness window), but the description plus schema cover what an agent needs to invoke it 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?

The schema covers the sole parameter 100%, including a full enum and a description that mirrors the default. The prose adds no new parameter semantics beyond restating the default, so the baseline of 3 applies.

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?

Opens with a specific verb and resource ('Get Los Angeles Times section headlines') and identifies the underlying source ('public Los Angeles Times section RSS feed'). This differentiates it from sibling article/author/sections tools by making clear it returns a per-section headline list, not article content or metadata.

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?

Implies use for fetching section-level headlines and states the default section ('section defaults to main'), but does not explicitly say when to prefer this over latimes_article, latimes_author, or latimes_sections. There is no alternative guidance or exclusions.

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