Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

thenextweb_article

Retrieve structured content from a canonical thenextweb.com/news article URL, including title, authors, body paragraphs, and paywall status.

Instructions

Get The Next Web article content. Returns one The Next Web article by url, which must be a canonical HTTPS thenextweb.com/news/<slug> link; off-site URLs and non-article paths are rejected. The response has the title, description, section, authors, publication and update times, image URL, body paragraphs and a paywalled flag.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical thenextweb.com article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.5/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 a good job: it discloses the rejection behavior for non-canonical URLs and enumerates the returned payload including a `paywalled` flag, which is genuinely useful non-obvious behavior. It omits auth requirements, rate limits, and error/empty-result handling, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each earning its place: purpose first, input constraint second, return shape third. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no annotations, so the description must cover both input constraints and return values — and it does, listing title, description, section, authors, timestamps, image URL, paragraphs, and the paywalled flag. Nothing an agent needs to call this correctly is missing.

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 already 100%, so the baseline is 3; the description goes beyond the terse schema text ('Canonical thenextweb.com article URL') by specifying the exact accepted shape (HTTPS, /news/<slug>) and what is rejected. It adds real constraint meaning rather than restating the schema.

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 The Next Web article content') and immediately scopes it to exactly one article keyed by URL. An agent can distinguish this from the sibling listing tools (thenextweb_headlines, thenextweb_news, thenextweb_sections) without opening any 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?

Gives a clear precondition (must be a canonical HTTPS thenextweb.com/news/<slug> link) and an explicit exclusion (off-site URLs and non-article paths are rejected), which is real when/when-not guidance. It does not, however, name the alternative tools to use for headline or section browsing, so it stops short of full routing guidance.

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