Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

forbes_author

Get a Forbes author's byline page data. Returns name, bio, headshot, and recent articles for journalist research.

Instructions

Forbes contributor/staff author profile. Returns one Forbes contributor or staff author's public byline page: name, display type, bio, headshot, and their most recent bylined articles. This is the journalist byline page at forbes.com/sites//, distinct from forbes-person, which is a billionaire net-worth profile from Forbes's rich-list data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoCanonical forbes.com/sites/<slug>/ URL, as an alternative to slug
slugNoForbes contributor slug, e.g. alisondurkee

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses what is returned (name, bio, headshot, recent articles) but does not mention potential limitations (e.g., empty results, pagination, error behavior). It doesn't contradict anything, but a read tool could benefit from stating that it returns only public byline data.

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?

The description is three sentences with no filler. It front-loads the core purpose, then details the returned content, and closes with a clear differentiation. Every sentence earns its place.

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?

Given there is no output schema, the description adequately explains what the tool returns. It also clarifies the URL structure and the distinction from forbes-person. It doesn't mention error cases or pagination, but for a simple lookup tool this is sufficient for an agent to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% – both 'slug' and 'url' have clear descriptions in the schema. The description adds little beyond that, only mentioning the example slug and URL format. Baseline of 3 applies since the schema already documents parameters thoroughly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it returns a Forbes contributor/staff author's public byline page with specific data (name, display type, bio, headshot, recent articles). It explicitly differentiates from forbes-person, making the purpose unambiguous and distinct from siblings.

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?

The description provides clear context by contrasting with forbes-person ('distinct from forbes-person, which is a billionaire net-worth profile'), effectively telling the agent when to use this tool instead. It doesn't exhaustively list all alternatives, but the explicit distinction is strong usage guidance.

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