Fetch section headlines from The Next Web using a section slug from the sections list, returning article cards for topics like fintech, startups, and policy.
Get The Next Web section headlines. Returns article cards from the public server-rendered section page. Pagination uses a robots-disallowed JSON path and is not requested.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | Editorial section slug returned by thenextweb_sections |
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 behavioral burden and does reasonably well: it discloses the return shape (article cards), the origin (public server-rendered page), and a concrete limitation (pagination deliberately skipped because the JSON path is robots-disallowed). It lacks auth or rate-limit notes, but for a public read endpoint this is solid disclosure.
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 before the return-shape and pagination caveats. The robots-disallowed pagination note is slightly technical but earns its place by preempting an attempt to paginate.
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, and the description compensates by naming the return artifact (article cards) and ruling out pagination. For a single-enum-parameter feed tool, that is near enough to call correctly, only missing an explicit sibling comparison.
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?
Schema coverage is 100% and the sole 'section' parameter has a full enum, so the schema does the heavy lifting. The description adds the useful provenance detail that the slug comes from thenextweb_sections, but provides no additional format or value semantics. Baseline 3 applies.
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+resource ('Get The Next Web section headlines') and clarifies the data source ('public server-rendered section page'). It does not explicitly distinguish itself from close siblings like thenextweb_news or thenextweb_sections, so an agent must infer the difference, but the core purpose is unambiguous.
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?
The description implies when to use it (a section slug obtained from thenextweb_sections) and notes a limitation (pagination not requested), but gives no explicit when/when-not versus thenextweb_news or thenextweb_article. Usage is inferable rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.