Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

thenextweb_author

Read-only

Fetch one public The Next Web author profile and its listed article cards; provide an author slug or canonical profile URL.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "thenextweb_author"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / slug / description
      Added value: +"Author slug from the public author sitemap or an article byline"
    • addedInput schema / properties / url / description
      Added value: +"Canonical thenextweb.com/author/<slug> URL; alternative to slug"
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true and openWorldHint=true, so the safety profile is given. The description adds that it returns a profile plus article cards (useful return-shape context), but doesn't disclose pagination, rate limits, or what happens with bad slugs. With annotations covering safety, this is adequate but thin.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One efficient sentence that front-loads the verb and resource, then names the inputs. No waste, no repetition.

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 read-only fetch tool with an output schema, annotations covering safety, and full schema coverage, the description is nearly complete. It states what's returned and what's needed to call it. Missing only edge-case behavior (invalid slug, empty results), which is a minor 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 coverage is 100%, and the description reinforces that either a slug or canonical URL works ('provide an author slug or canonical profile URL'). It adds value by clarifying the two are alternatives, which the schema hints at but the description states explicitly.

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?

States a specific verb ('Fetch') and resource ('one public The Next Web author profile and its listed article cards'). The scope is clear. However, it doesn't explicitly distinguish this author tool from the hundreds of sibling `*_author` tools beyond the implicit site prefix, and it doesn't mention what differentiates it from `thenextweb_article`/`thenextweb_headlines` beyond the resource name.

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?

Provides clear input requirements ('provide an author slug or canonical profile URL'), which tells the agent what it needs to call the tool. But it doesn't say when to choose this tool over alternatives (e.g., article tools) or note any prerequisites like needing an author slug first from an article byline.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources