Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fastcompany_author

Retrieve a Fast Company contributor's name, biography, and recent articles from a canonical profile URL. Use it to gather public author details without bypassing access controls.

Instructions

Get a Fast Company contributor profile. Returns a Fast Company contributor's name, biography, and recent articles from a canonical contributor URL. The biography is omitted if the contributor's profile page cannot be loaded. It does not bypass authentication or access controls.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Fast Company contributor URL

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, the description carries the full burden and does add real behavioral context: the exact return contents and the conditional failure mode ('biography is omitted if the contributor's profile page cannot be loaded'). It also states it does not bypass authentication or access controls. It stops short of rate limits or more explicit auth requirements, so not a 5.

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 tight sentences, front-loaded with the core purpose, then return shape, then failure mode. Nearly every clause earns its place; only the safety line is somewhat boilerplate for a read-only fetch.

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 single-param scraper with no annotations and no output schema, the description covers return fields and the degraded-result case, which is what an agent needs to interpret the response. Missing only pagination/limit behavior, which is a minor gap.

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 coverage is 100% and there is a single well-named parameter whose description already specifies 'Canonical Fast Company contributor URL'. The prose adds only the same 'from a canonical contributor URL' phrasing, so the baseline 3 applies when the schema does the work.

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?

States a specific verb and resource ('Get a Fast Company contributor profile') and enumerates the returned payload (name, biography, recent articles). An agent can readily distinguish this from siblings like fastcompany_article and fastcompany_news.

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 required 'canonical contributor URL' input, but the description never says when to choose this over fastcompany_article/fastcompany_news nor states prerequisites or exclusions. Adequate but leaves routing to inference.

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