Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

foxnews_headlines

Fetch current Fox News headlines from a selected RSS section; provide a section slug like us, world, politics, health, or tech to receive structured article titles.

Instructions

Get Fox News section headlines. Returns fresh headlines from one public Fox News article RSS section. Use foxnews-sections for the current value space.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionYesFox News RSS section slug: us, world, politics, science, health, sports, travel, tech, opinion, entertainment, media, or lifestyle

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It discloses that the source is public, that results are 'fresh,' and that it covers one RSS section. However, it does not mention output format, pagination, caching, or error behavior, leaving some behavioral gaps.

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?

The description is two sentences with no filler. The main action is front-loaded, and the pointer to foxnews-sections is a valuable addition that does not waste space.

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 low-complexity tool with one fully described enum parameter and no output schema, the description covers the key context: what it returns (headlines), the source scope (one public RSS section), and where to find valid values. A minor gap is the lack of an explicit statement about the output structure, but the simplicity of the tool makes this acceptable.

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%, so the schema fully documents the 'section' parameter including the enum values. The description adds only the context that it is a single RSS section and that foxnews-sections provides the current value space—useful but not meaningfully beyond the schema.

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?

The description uses a clear verb-resource pair: 'Get Fox News section headlines' and further specifies the scope as 'one public Fox News article RSS section.' It distinguishes itself from siblings by noting the single-section RSS source and by pointing to foxnews-sections for the value space.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context that this tool is for per-section headlines and explicitly routes to 'foxnews-sections for the current value space.' It lacks explicit 'when not to use' guidance for sibling tools like foxnews_news or foxnews_article, but the single-section RSS framing makes the intended use clear.

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