Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

businessinsider_author

Fetch a Business Insider author profile using a slug or canonical URL; get name, job title, bio, image, social accounts, and recent articles.

Instructions

Get a Business Insider author profile. Returns a Business Insider author's profile, identified by slug (the last segment of the author's page address) or a canonical https://www.businessinsider.com/author/<slug> url; exactly one is required. The response has name, job title, bio, image, social_accounts and one page of recent articles with title, URL and summary. Accounts the author does not list are simply absent.

Input Schema

NameRequiredDescriptionDefault
urlNoCanonical businessinsider.com/author/<slug> URL; alternative to slug
slugNoAuthor slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/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 and does so reasonably: it discloses the return shape (name, job title, bio, image, social_accounts, recent articles), notes the article list is limited to 'one page', and flags that unlisted accounts are simply absent. It does not mention error behavior for an invalid slug or whether the call is safe/read-only, but the core behavior is communicated.

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?

Two sentences, front-loaded with the purpose followed by identification rules and return contents. The first sentence lightly restates the opening clause, but nothing else is wasted and the density of useful information is high.

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 by enumerating the response fields and the one-page article limit, and it covers both input modes and the required-either-one rule. Only minor gaps remain, such as failure behavior for a malformed slug, which are acceptable for this simple lookup tool.

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 already 100%, so the baseline is 3, but the description adds real meaning on top: `slug` is defined as the last segment of the author's page address, `url` as the canonical `businessinsider.com/author/<slug>` form, and the exactly-one-of constraint is stated. That is more than the schema alone conveys.

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 names a specific verb and resource ('Get a Business Insider author profile') and distinguishes the author resource from the sibling article/headline/news tools by naming the entity type. It stops short of explicitly routing away from siblings, but an agent can tell it retrieves author profiles rather than articles.

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 that exactly one of `slug` or `url` must be supplied, which is useful selection guidance, but it never says when to reach for this tool versus `businessinsider_article`/`businessinsider_headlines`, nor where a slug typically comes from. Usage is implied rather than stated.

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