Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

businessinsider_article

Retrieves a Business Insider article by canonical URL, returning its title, description, authors, image, and body paragraphs. Subscriber-only or blocked content returns an error instead of partial text.

Instructions

Get Business Insider article content. Returns a Business Insider article by canonical url: title, description, publication and update times, section, authors, image and the body paragraphs. Subscriber-only or blocked content returns an error instead of partial text.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Business Insider article 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?

With no annotations, the description carries the full burden, and it does useful work: it enumerates the returned fields and, importantly, discloses that subscriber-only or blocked content 'returns an error instead of partial text.' That failure mode is genuinely helpful. It does not cover auth, rate limits, or anything about caching, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the purpose, then the return shape, then the error condition. No filler, and each sentence earns its place.

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?

There is no output schema, so the description compensates by listing the returned fields (title, description, times, section, authors, image, body paragraphs) and by covering the error behavior. An agent has everything needed to call it and interpret the result.

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% with a single required `url` parameter, so the schema already documents it fully. The description repeats 'canonical `url`' without adding format details or examples beyond what the schema provides. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Get') and resource ('Business Insider article content'), then enumerates the returned fields. This clearly distinguishes it from sibling list tools like businessinsider_headlines and businessinsider_news, which return collections rather than a single article.

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?

The description implies usage by stating it takes a canonical `url` and returns a single article, and it discloses the subscriber-only error path. However, it never explicitly contrasts this with sibling tools (headlines/news/sections) or states the prerequisite of having a canonical URL in hand, leaving 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