Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

newsmax_author

Fetch a Newsmax Insiders author profile from a canonical URL, returning name, biography, image, and recent columns.

Instructions

Get a Newsmax Insiders author profile. Returns a Newsmax Insiders (opinion columnist) profile from a required url such as https://www.newsmax.com/insiders/<slug>/id-<id>/. The response has name, biography, image_url and recent columns. biography is omitted when Newsmax's separate profile page is unavailable, and article published_at is date text such as Sep 23, 2026.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Newsmax Insiders author URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.1/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 load and does well: it enumerates the return fields, discloses that `biography` is conditionally omitted when the separate profile page is unavailable, and specifies that `published_at` is date text like `Sep 23, 2026`. It stops short of noting auth or error behavior, but covers the key non-obvious traits.

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 tight sentences, front-loaded with the purpose and then the URL requirement and return shape. Each sentence earns its place, with only mild redundancy from restating that it is a 'Newsmax Insiders' tool.

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 must describe returns, which it does by listing name/biography/image_url/columns. The edge case around `biography` and the date format round out an otherwise complete picture for a simple single-param fetch.

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% for the single `url` param, so the baseline is 3, and the description adds a concrete example URL pattern (`https://www.newsmax.com/insiders/<slug>/id-<id>/`) that clarifies the expected format beyond the schema's terse description.

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 (Get) and resource (Newsmax Insiders author profile) with a precise scope, and distinguishes itself from the sibling newsmax_article/newsmax_headlines/newsmax_news tools by targeting the author entity rather than content.

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?

The requirement of a canonical Insiders URL implies when this tool applies, but it never states when to prefer it over alternatives or what the input cannot be. Usage is implied rather than guided.

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