Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

breitbart_article

Retrieve a Breitbart article by canonical URL and get its title, authors, timestamps, section, image, and body paragraphs in structured JSON.

Instructions

Get Breitbart article content. Returns a Breitbart article by url, a canonical https://www.breitbart.com/<section>/<yyyy>/<mm>/<dd>/<slug>/ address. The response has the title, description, publication and update times, section, image, authors and the body paragraphs.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Breitbart article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It discloses the return shape (title, description, times, section, image, authors, paragraphs), which is valuable, and 'Get' implies a read. However it says nothing about side effects, auth, or error behavior for malformed/non-canonical URLs.

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?

Two sentences, front-loaded with the purpose before the return details, and no filler. Every clause earns its place given there is no output schema to fall back on.

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 no output schema and no annotations, the description compensates by enumerating the returned fields and the required URL format, which is enough to call it correctly. It could be more complete by noting failure behavior for non-canonical URLs.

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% and the schema only says 'Canonical Breitbart article URL'. The description goes beyond that by spelling out the URL pattern (https://www.breitbart.com/<section>/<yyyy>/<mm>/<dd>/<slug>/), which helps an agent construct a valid input.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get Breitbart article content') and pins down that it operates on a single article by URL, which cleanly separates it from breitbart_headlines/news/sections. It stops short of naming those siblings, so the differentiation is inferable rather than explicit.

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?

Requiring a canonical article URL implies the tool is used when you already have one, but the description never states when to prefer this over breitbart_headlines or breitbart_news, nor any exclusion. Usage is implied, not guided.

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