Retrieve The Next Web's ten editorial sections from its homepage navigation, excluding topic archives, media, events, and promotional categories.
Get The Next Web sections. Returns the ten editorial sections in The Next Web's current homepage navigation. Topic/tag archives, media, events and promotional categories are excluded.
| 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 behavioral burden. It discloses what is returned (ten editorial sections) and what is deliberately excluded, which is genuinely useful, but says nothing about auth requirements, response format, ordering, or stability of the section list.
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?
Two short sentences with the verb and resource front-loaded, followed immediately by the return content and scope exclusions. There is no filler or redundancy, though the exclusions clause slightly blurs whether it is describing the return value or usage constraints.
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?
For a zero-parameter, read-only listing tool with no output schema, the description gives enough to call it correctly and even characterizes the returned set. What is missing (response shape, ordering) is minor given the tool's simplicity and lack of annotations.
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 takes zero parameters and the schema is empty with 100% coverage, so there is nothing for the description to clarify. The baseline for a no-parameter tool is 4, and no parameter confusion is possible.
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?
States a specific verb and resource ("Get The Next Web sections") and adds useful scope: the ten editorial sections in the current homepage navigation, with topic/tag archives, media, events and promotional categories excluded. This clearly differentiates the tool from article/headline tools contextually, but it never names the relevant siblings (thenextweb_headlines, thenextweb_news), so it stops short of full sibling disambiguation.
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?
Usage is implied by the content description (fetch the site's top-level editorial navigation), but there is no explicit when-to-use guidance, no statement of when to prefer headlines/news instead, and no prerequisites. The exclusion note hints at scope boundaries but does not route the agent between alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.