Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cbr_article

Fetch a CBR article by canonical URL to get title, description, authors, publication details, image, and body paragraphs; invalid section, video, author, or category pages are rejected.

Instructions

Get CBR article content. Returns a CBR article by url, a canonical cbr.com address of the form /<slug>/: title, description, publication and update times, section, authors, image and the body paragraphs. Section, video, author and category pages are rejected as invalid. paywalled is true only if the page declares the article not free, and then paragraphs may be a teaser.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical CBR article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/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 delivers well: it enumerates the returned fields, discloses paywall semantics ('paywalled' true only when the page declares the article not free, paragraphs may be a teaser), and states which page types are rejected. Auth, rate limits, and pagination are unaddressed.

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?

Three tightly packed sentences with zero filler, front-loaded with the core action and return shape. Every sentence adds information the agent needs (return fields, invalid inputs, paywall behavior).

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

Completeness5/5

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

With no output schema, the description appropriately documents the return payload (title, description, times, section, authors, image, paragraphs) plus the paywall caveat. Nothing an agent needs to invoke it correctly is missing.

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%, so the baseline is 3, but the description adds real meaning beyond the schema's 'Canonical CBR article URL' by specifying the exact form `/<slug>/`, which helps the agent construct a valid argument.

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 CBR article content') and names exactly what is returned. It implicitly distinguishes itself from siblings like cbr_sections, cbr_author, cbr_headlines by declaring that section, video, author and category pages are rejected.

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?

Provides clear negative guidance: section, video, author and category pages are invalid inputs, which tells the agent when not to use this tool. It does not name a specific alternative sibling to route to for those pages, keeping it just short of a 5.

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