Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

thenextweb_headlines

Fetch headlines and story cards from a chosen The Next Web editorial section by providing its required section slug, like deep-tech or fintech-ecommerce.

Instructions

Get The Next Web section headlines. Returns the story cards of one The Next Web editorial section. section is required and must be one of deep-tech, sustainability, ecosystems, data-security, fintech-ecommerce, future-of-work, startups-technology, investors-funding, government-policy or corporates-innovation; other values return a 400.

Input Schema

NameRequiredDescriptionDefault
sectionYesEditorial section slug returned by thenextweb_sections

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It discloses the return shape ('story cards') and a concrete failure mode (400 on invalid section), which is useful, but says nothing about pagination, auth, rate limits, or how many stories are returned.

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 the purpose, then scope, then the parameter constraint. Three tight sentences that each carry information; the only minor redundancy is restating the scope ('one The Next Web editorial section') that the opening line already implies.

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-required-parameter read tool with no output schema, the description is nearly sufficient: it names the resource, the required input, and the failure mode. It could state the shape/count of the returned 'story cards,' but nothing an agent needs to select and call it 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 100% and the enum is already in the schema, so restating the values earns no credit. However, the description adds the non-obvious behavioral fact that out-of-enum values return a 400 rather than empty results, which is genuine meaning beyond 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+resource ('Get The Next Web section headlines') and clarifies the scope ('one The Next Web editorial section'), which distinguishes it from siblings like thenextweb_news (all news) and thenextweb_article (single story). An agent can identify the tool without opening the 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 explicit input constraints and error semantics: 'section' is required, must match a listed value, and 'other values return a 400.' It does not explicitly contrast this tool against thenextweb_news or thenextweb_sections, but the scoping to a single editorial section gives clear context.

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