Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

newsmax_headlines

Fetch recent Newsmax headlines for a specified section slug, returning story titles, URLs, and optional summaries, authors, publication times, and images.

Instructions

Get Newsmax section headlines. Returns recent Newsmax stories for one section. section is required and takes one of 20 slugs, such as newsfront, politics, health-news, finance-news or insiders. Each item has a title and URL, and may include summary, author, publication time and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesNewsmax RSS section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.5/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 full load. It helpfully describes the return shape (title and URL, optionally summary/author/publication time/image), but says nothing about pagination, result limits, authentication, or caching — the operational traits an agent would want for a feed 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 compact sentences, front-loaded with the core action and scope. No wasted phrasing; the return-field sentence earns its place because there is no output schema.

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, read-only feed tool with no output schema, the description covers purpose, scope, parameter domain, and return fields adequately. Minor gaps (pagination, result count) remain but are low stakes.

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 fully enumerates all 20 slugs, so the schema already documents the parameter. The description's slug examples add convenience but no meaning beyond the schema — 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?

The description names a specific verb and resource: 'Get Newsmax section headlines' and 'Returns recent Newsmax stories for one section.' This distinguishes it from siblings like newsmax_news (all news) and newsmax_sections (list of sections), though it never names those alternatives explicitly.

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 by the scope ('for one section'), but the description gives no explicit when-to-use or when-not-to-use guidance relative to newsmax_news, newsmax_article, or newsmax_sections. An agent must infer the routing.

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