Crawlora MCP

thenextweb_headlines

Read-only

Fetch article cards from one public The Next Web server-rendered section page; provide a slug from thenextweb_sections. Robots-disallowed JSON pagination is not used.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "section": "<section>"
    },
    "name": "thenextweb_headlines"
  }
}

Input Schema

Name	Required	Description	Default
`section`	Yes	Editorial section slug returned by thenextweb_sections. Documented values: deep-tech, sustainability, ecosystems, data-security, fintech-ecommerce, future-of-work, startups-technology, investors-funding, government-policy, corporates-innovation.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026

addedInput schema / properties / section / description

Added value: +"Editorial section slug returned by thenextweb_sections. Documented values: deep-tech, sustainability, ecosystems, data-security, fintech-ecommerce, future-of-work, startups-technology, investors-funding, government-policy, corporates-innovation."

First observedOct 7, 2026

TDQS

A3.6/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds a genuine behavioral note — the "Robots-disallowed JSON pagination is not used" — implying first-page-only scraping, but does not explain result limits or ordering.

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?

A single semicolon-joined sentence, front-loaded with the action and resource, then the parameter source, then a caveat. Efficient with little waste.

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?

An output schema exists, so return-value explanation is unnecessary, and the single required parameter is fully documented. The definition is adequate for this simple fetch tool, needing only clearer sibling differentiation to be complete.

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

Parameters3/5

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

Schema description coverage is 100% and the schema already enumerates the documented section slugs. The description only restates that section comes from thenextweb_sections, adding no syntax or format detail beyond the schema. Baseline 3 applies.

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 ("Fetch article cards") and resource with scope ("one public The Next Web server-rendered section page"), and names the sibling thenextweb_sections as the source of the slug. It differentiates from a generic feed but never contrasts with thenextweb_news or thenextweb_article.

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?

Provides a clear prerequisite — the section slug must come from thenextweb_sections — which gives the agent enough context to invoke correctly. It does not, however, state when to prefer this over thenextweb_news or thenextweb_article.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.