Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

newsmax_news

Fetch Newsmax top stories from the Newsfront section. Returns each story's title, URL, and optional summary, author, publication time, or image for quick news monitoring.

Instructions

Get Newsmax top stories. Returns the current Newsmax top stories from the Newsfront section, with no parameters. Each item has a title and URL, and may include summary, author, publication time and image. Use newsmax-headlines for other sections.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/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 full burden. It discloses that the tool takes no parameters, returns the current top stories, and enumerates the fields each item contains (title, URL, and optionally summary, author, publication time, image) — meaningful behavioral context in the absence of an output schema. It does not address caching/freshness or rate limits, but for a static read-only feed endpoint this is close to sufficient.

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?

Front-loaded with the core action and scoped tightly to three sentences. Minor redundancy: "Returns the current Newsmax top stories from the Newsfront section" restates the opening sentence's "Get Newsmax top stories."

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?

With no annotations and no output schema, the description does the necessary work by naming the source section, the item fields, and the sibling alternative. Only the slightly incorrect/ambiguous sibling reference ("newsmax-headlines" vs. newsmax_headlines/newsmax_sections) keeps it from being fully self-contained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, so the schema has nothing to explain; per the rubric this is a baseline 4. The description's "with no parameters" merely confirms the empty schema rather than adding new meaning.

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?

States a specific verb and resource ("Get Newsmax top stories") and narrows the scope to the Newsfront section, which distinguishes it from the sibling newsmax_headlines/newsmax_sections tools. An agent can identify the tool without opening the schema.

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?

Explicitly routes the agent to an alternative ("Use `newsmax-headlines` for other sections"), giving a clear when-to-use-this-vs-that signal. The guidance is slightly muddled because the sibling list also contains newsmax_sections, so "other sections" is ambiguous about which alternative to pick, and the name is written with a hyphen rather than the actual tool name.

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