Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

newsmax_article

Extract structured Newsmax article content by canonical URL, returning title, description, authors, publication times, and body paragraphs. Rejects paywalled Platinum URLs.

Instructions

Get Newsmax article content. Returns a Newsmax article by canonical url in the form /<section>/<slug>/YYYY/MM/DD/id/<id>: title, description, section, authors, lead image, publication and update times, and body paragraphs. authors may be empty for wire or staff-aggregated stories. Paywalled Platinum URLs are not accepted.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Newsmax article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.9/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 does reasonably well: it discloses the returned field set, notes that `authors` may be empty for wire/aggregated stories, and warns that paywalled Platinum URLs are rejected. It omits auth, rate-limit, or error behavior, but for a read-only fetch this is solid disclosure.

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?

Three sentences, front-loaded with the core action, followed by return fields and then edge cases. Every sentence carries information; nothing is redundant.

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?

No output schema exists, so the description correctly enumerates the return payload (title, description, section, authors, image, times, paragraphs) and covers the main edge cases. It is nearly complete for a one-parameter fetch tool, lacking only pagination/error semantics that are largely irrelevant here.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine value beyond the schema's terse 'Canonical Newsmax article URL' by spelling out the required path shape `/<section>/<slug>/YYYY/MM/DD/id/<id>` and noting which URLs are invalid.

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 Newsmax article content') and enumerates the fields returned, making it clearly an article-detail fetcher. It does not explicitly name the sibling tools it replaces (newsmax_headlines, newsmax_news, newsmax_sections), so differentiation is left to inference from the name.

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 — fetch a single article given its canonical URL — and there is one useful exclusion ('Paywalled Platinum URLs are not accepted'). However, it never states when to prefer this over newsmax_headlines/news/sections or what input source produces a valid URL.

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