Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

newsweek_article

Fetch a Newsweek article by canonical newsweek.com URL with numeric ID. Returns title, authors, publication dates, paywall flag, and body paragraphs as clean JSON.

Instructions

Get Newsweek article content. Returns a Newsweek article by canonical url, which must be a newsweek.com link ending in a numeric article id. The response has title, description, section, authors, lead image, publication and update times, a paywalled flag and body paragraphs.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Newsweek article 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?

No annotations are provided, so the description carries the full burden, and it does reasonably well: it discloses the response fields (title, description, section, authors, lead image, publication/update times, paywalled flag, body paragraphs), with the paywalled flag being meaningful behavioral context an agent should know. It does not cover auth requirements or rate limits, keeping it short of a 5.

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 purpose, then the input constraint, then the return shape. Three compact sentences with no obvious filler, though the return-field list is dense enough that it slightly crowds the structure.

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 tool with no output schema and no annotations, the description supplies the essential input constraint and a useful inventory of return fields. Nothing critical to calling it correctly is missing, though auth/rate-limit behavior is unaddressed.

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% (the schema documents url as 'Canonical Newsweek article URL'), so baseline is 3. The description adds real meaning beyond the schema by requiring the exact form: a newsweek.com link ending in a numeric article id, which helps the agent supply a valid value.

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 (Newsweek article content), clearly distinguishing it from sibling tools like newsweek_news, newsweek_headlines, and newsweek_author. An agent knows this retrieves a single article by URL.

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 description constrains usage by specifying that the url must be a canonical newsweek.com link ending in a numeric article id, which is genuinely useful. However, it does not state when to choose this over sibling article-adjacent tools (newsweek_headlines/newsweek_news), so usage is implied rather than explicit.

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