Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fortune_author

Fetch a Fortune author's public profile, including name, bio, email, social accounts, and recent articles. Provide a slug or fortune.com author URL to retrieve the data.

Instructions

Get a Fortune author profile. Returns one Fortune author's public profile: name, bio, email, social accounts, and one page of their recent articles (30 fortune.com/2026-format article dates use "Month D, YYYY"; converted to YYYY-MM-DD here).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoCanonical fortune.com/author/<slug>/ URL, optionally with a /page/<n>/ suffix; alternative to slug
pageNo1-based page number; overrides any page number in url
slugNoAuthor slug, e.g. sheryl-estrada

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does well by stating the exact output shape (one profile, listed fields, one page of up to 30 articles) and even calling out the date format conversion to YYYY-MM-DD, which is genuinely useful behavioral context. Minor gaps include lack of error/null-field behavior.

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?

The description is compact and front-loads the purpose and return contents. The parenthetical about date conversion is slightly awkward but conveys an important output-format detail without excessive length.

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 simple all-optional 3-parameter tool with 100% schema coverage and no output schema, the description is largely complete. It names the returned fields and the pagination/date-conversion behavior, so an agent has what it needs to invoke the tool correctly. Error behavior for unknown authors is not described but is not essential.

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%, so the baseline is 3. The description adds little about parameter semantics; it mostly describes output behavior. The three parameters (url, page, slug) are already well-documented in the schema.

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 opens with a specific verb and resource ('Get a Fortune author profile') and enumerates the returned fields (name, bio, email, social accounts, one page of recent articles). This clearly differentiates it from sibling tools like fortune_article and other outlet-specific 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?

Usage is implied by the purpose—call this when you need a Fortune author's profile and their recent articles—but there is no explicit guidance on when to prefer this over alternatives, nor any direction on choosing among slug, URL, or page parameters beyond the schema.

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