Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

abcnews_headlines

Fetch current ABC News headlines for a chosen section such as us, world, politics, business, technology, entertainment, health, or sports, returning titles, URLs, and optional summaries.

Instructions

Get ABC News section headlines. Returns the current headlines for one ABC News section. section is required and must be us, world, politics, business, technology, entertainment, health or sports. Each item has a title and URL, and may also carry a summary, author, publication time and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesABC News 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 full burden, and it does disclose the return shape in detail: each item has a title and URL, and may carry summary, author, publication time and image. This compensates well for the absent output schema. It does not mention freshness/caching, pagination, or that it is a read-only snapshot, leaving some behavioral context unstated.

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?

Three front-loaded sentences that move from purpose to required argument to return shape, with no filler. The enum re-listing is somewhat redundant against the schema but does not bloat the text excessively.

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 simple one-parameter read tool with no output schema, the description covers purpose, the required argument, and return contents. It is essentially complete for correct invocation; only minor behavioral details (freshness, pagination) are missing.

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% – the enum and required flag are already fully specified in the schema. The description restates the allowed values and that section is required, adding no syntax or meaning beyond the structured field. Baseline 3 is appropriate.

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 ABC News section headlines') and scopes it to 'one ABC News section', which implies the single-section scope. It does not explicitly contrast with sibling tools like abcnews_news or abcnews_sections, so the reader must infer the distinction rather than being told it.

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 only implied: the section enumeration makes it clear this is for pulling a specific section's headlines, but there is no explicit when-to-use / when-not-to-use guidance and no named alternative (e.g., abcnews_news for all sections). Adequate but with a clear gap.

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