Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

thenextweb_author

Get The Next Web author profile by slug or canonical URL. It returns the author's name, image URL, and article story cards with titles, links, summaries, and publication times.

Instructions

Get a The Next Web author profile. Returns a The Next Web author's name, image URL and the story cards on their archive page. Give slug or a canonical thenextweb.com/author/<slug> url; slug is required when url is omitted. Each article has a title, URL, summary, author, image, type and publication time.

Input Schema

NameRequiredDescriptionDefault
urlNoCanonical thenextweb.com/author/<slug> URL; alternative to slug
slugNoAuthor slug from the public author sitemap or an article byline

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It helpfully discloses the payload contents (author name, image URL, story cards, and per-article fields), but says nothing about pagination of the archive page, result limits, or whether any auth/rate limits apply.

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?

Three sentences, front-loaded with purpose, then input rule, then return fields; each sentence earns its place. The per-article field enumeration is slightly list-heavy but justified because no output schema exists.

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?

With no output schema and no annotations, the description compensates well by describing both the profile fields and the article card fields, plus the slug/url dependency. It stops short of covering pagination or archive size, which is the remaining gap.

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 description coverage is 100%, so the baseline is 3, but the description adds a real constraint the schema does not express: although `required` is empty, `slug` becomes required when `url` is omitted. That conditional dependency is meaningful value beyond the schema.

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?

The description gives a specific verb+resource ("Get a The Next Web author profile") scoped to one publisher, and the return shape (name, image URL, story cards) makes clear it is not the article or headlines tool. It does not explicitly name a sibling alternative, but the domain-qualified naming separates it cleanly from the many other `_author` tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the input rule ("Give `slug` or a canonical ... `url`; `slug` is required when `url` is omitted"), which is useful selection guidance for parameters. However, there is no guidance on when to use this tool versus `thenextweb_article`, `thenextweb_news`, or `thenextweb_headlines`, so usage context is only implied.

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