Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cbr_author

Retrieve a CBR author profile from a canonical URL to get name, title, bio, image, social links, and about 20 latest items; paginated URLs are rejected.

Instructions

Get a CBR author profile. Returns a CBR author profile from url, a canonical https://www.cbr.com/author/<slug>/ address; paginated /page/N/ URLs are rejected. The response has name, title, biography, image, social_links and about 20 items from the profile's Latest module, with no older pages available.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical CBR author URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.1/5.0
Behavior4/5

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

No annotations exist, so the description carries full disclosure, and it does well: it names the exact fields returned (name, title, biography, image, social_links), quantifies the Latest module (~20 items), and warns that older pages are unavailable and paginated URLs are rejected. It omits error behavior for malformed but non-paginated URLs, keeping it short of 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?

The purpose statement is front-loaded and every sentence carries information (input format, validation constraint, return shape). There is mild redundancy between 'Get a CBR author profile' and 'Returns a CBR author profile from url', but nothing is bloated.

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 one well-documented parameter, no annotations, and no output schema, the description must supply the return shape itself, and it does. The only shortfall is the absence of any error/failure guidance beyond URL rejection, which is minor for a simple read 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 100% ('Canonical CBR author URL'), so the baseline is 3, but the description adds genuine meaning: the exact canonical format `https://www.cbr.com/author/<slug>/` and the explicit rejection of `/page/N/` variants. That tells an agent how to construct a valid value rather than just naming the parameter.

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+resource ('Get a CBR author profile') that is unambiguously distinct from sibling CBR tools like cbr_news, cbr_sections and cbr_article. An agent knows immediately this returns a single author's profile rather than an article or section listing.

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 rather than stated: it accepts a canonical author URL and rejects paginated `/page/N/` URLs, which hints at the correct input shape. However, it never says when to reach for this tool vs. related siblings, nor describes how an agent should obtain a canonical author URL in the first place.

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