Fetch current top stories from The Next Web, including title, canonical URL, summary, author, publication time, and image URL when available.
Get The Next Web top stories. Returns the current top stories from The Next Web. It takes no parameters. Each item has the publisher's title, canonical URL, summary, publication time and author, plus the image URL when one is present.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.9Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden, and it does add value by enumerating the return fields (title, canonical URL, summary, publication time, author, conditional image URL) and confirming it takes no parameters. However, it omits operational traits such as number of items returned, freshness/update cadence, or pagination, which matter for a feed tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences, front-loaded with the purpose and return shape. The first two sentences are somewhat redundant ('top stories' restated as 'current top stories'), which costs a bit but overall the text is tight.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
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 carries the burden of describing return values, and it does so adequately by listing each field. For a no-parameter news feed it is nearly complete, missing only item count and update cadence.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-param tool applies. The explicit note that it 'takes no parameters' is consistent with the empty schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The opening sentence states a specific verb+resource ('Get The Next Web top stories') and the second sentence confirms the resource is the current top stories feed. It is clear what the tool does, but it never distinguishes itself from close siblings like thenextweb_headlines, thenextweb_article, or thenextweb_sections, so an agent cannot tell which to pick from the description alone.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use guidance, no exclusion of alternatives, and no mention of the very similar thenextweb_headlines sibling. The agent is left to infer routing entirely from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.