Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bleacherreport_author

Retrieve a Bleacher Report writer's public profile with name, role, biography, photo, and recent stories by supplying the writer's URL or slug.

Instructions

Get a Bleacher Report writer profile. Returns one Bleacher Report writer's public profile: name, role, biography, photo, and the latest stories listed on the page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoCanonical bleacherreport.com/writers/<slug> URL; alternative to slug
slugNoWriter slug, e.g. scott-polacek

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description must carry the transparency burden. It discloses that the profile is public and lists returned fields, implying a read-only operation. However, it does not mention error cases, authentication needs, or behavior when a writer is not found, which are minor gaps for a simple fetch.

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 a single, efficient sentence that front-loads the core purpose and then lists the returned fields. There is no redundancy or filler, making it easy for an agent to quickly parse.

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?

Given the two optional parameters and lack of an output schema, the description is adequate but leaves a small gap: it does not clarify that either url or slug should be provided, nor what happens if neither is supplied. This is a minor omission for an otherwise straightforward tool.

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 both parameters are already well-documented in the schema. The description does not add additional meaning beyond what the schema provides, such as guidance on selecting between url and slug or whether at least one is required. Baseline 3 applies.

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 verb ('Get'), the resource ('a Bleacher Report writer profile'), and lists the exact fields returned (name, role, biography, photo, latest stories). This unambiguously distinguishes it from sibling tools like bleacherreport_article (which fetches articles) and other site-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 Guidelines4/5

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

The purpose is evident from the description and tool name: use this when you need a Bleacher Report writer's profile. It does not explicitly mention alternatives or exclusions, but the clear context is sufficient for an agent to select it appropriately among many sibling author tools.

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