Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rawstory_author

Retrieve a Raw Story author's public profile including bio, avatar, social links, and their 15 most recent stories by providing the author's slug or profile URL.

Instructions

Get a Raw Story author profile. Returns one Raw Story author's public profile: name, bio, avatar, public social links, and their 15 most recent stories.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoCanonical rawstory.com/u/<slug> URL; alternative to slug
slugNoAuthor slug, e.g. bennitokelty

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the returned data content but does not mention any side effects, limitations, authentication needs, or error behavior. For a simple read-only profile fetch, the lack of explicit non-mutating disclosure is a minor gap.

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?

A single sentence efficiently communicates purpose and output. It is front-loaded with the action and immediately specifies the result contents. No wasted words, though it could be slightly more compact by dropping 'public profile' redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with no output schema, the description covers the key return fields but omits practical details like how to obtain the slug/URL, any rate limits, or potential error states. It is adequate but not exhaustive for a non-trivial call.

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 'url' and 'slug' have clear descriptions. The tool description adds no additional parameter context beyond what the schema already provides, so the baseline of 3 is appropriate.

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 the action ('Get a Raw Story author profile') and specifies the resource (Raw Story author). It also enumerates the exact output fields (name, bio, avatar, social links, 15 most recent stories), making the tool's purpose unambiguous and distinct from other publisher-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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given on when to use this tool versus alternatives (e.g., other author tools) or when not to use it. The tool's scope is implied by the 'Raw Story' branding, but there is no explicit statement of selection criteria or exclusions.

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