Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

foxnews_headlines

Fetch Fox News headlines for a chosen section (e.g., politics, tech) and return 25 items with title, URL, summary, publication time, and image.

Instructions

Get Fox News section headlines. Returns the latest 25 Fox News headlines for one section. section is required and must be one of us, world, politics, science, health, sports, travel, tech, opinion, entertainment, media or lifestyle. Each item has its title, URL, summary, publication time and image.

Input 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

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It usefully discloses the fixed return size ('latest 25') and the per-item fields, which is real behavioral information, but it says nothing about caching/refresh behavior, auth or rate limits for a read-only RSS-backed tool.

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 short sentences, front-loaded with the verb and resource; nothing is padded. The inline list of section slugs duplicates the schema enum, which is the only mild waste.

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 list tool with no output schema, the description covers what is needed: the operation, the required parameter, the result count and the item shape. Remaining gaps (ordering beyond recency, error behavior for bad input) are minor.

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 lists all twelve slugs, so the description's enumeration of `section` values is largely redundant with the schema. It adds no syntax, default or format meaning beyond what the schema provides; baseline 3 applies.

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 Fox News section headlines') plus scope ('latest 25 ... for one section'), so the operation is unambiguous. It does not differentiate itself from other Fox News siblings such as foxnews_news, foxnews_sections or foxnews_search, so an agent still has to infer which one to pick.

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

Usage Guidelines2/5

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

The description says `section` is required and enumerates valid values, but that is a parameter constraint rather than usage guidance. There is no statement of when to use this tool versus foxnews_news, foxnews_sections or foxnews_search, and no exclusions or prerequisites.

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