Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

breitbart_headlines

Fetch current Breitbart section headlines by required slug, such as politics or border, to monitor one hub's stories.

Instructions

Get Breitbart section headlines. Returns current headlines from one Breitbart section hub. section is required and takes one of 21 slugs, such as politics, border, the-media or europe. The world-news, news and on-the-hill-exclusive-video hubs aggregate stories, so their links point to articles under whichever section owns each story.

Input Schema

NameRequiredDescriptionDefault
sectionYesBreitbart section slug

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?

With no annotations, the description carries the full burden. It discloses the genuinely useful aggregation quirk (world-news/news/on-the-hill links point to stories under their owning sections) and that it returns current headlines, but says nothing about count, ordering, pagination, or rate limits.

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, all front-loaded: purpose first, required parameter and examples second, behavioral caveat last. No filler and every sentence carries information.

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?

For a single-param, no-output-schema read tool, the description covers what it does, what the parameter accepts, and one important behavioral exception. It is largely complete; only minor gaps like result volume/ordering remain.

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 already 100% with an enum, so the baseline is 3. The description adds real meaning: it states the count (21 slugs), gives representative examples, and warns that three specific enum values behave as aggregators - information the schema itself does not convey.

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 section headlines') and clarifies it returns headlines from a single section hub. However, it never differentiates itself from siblings like breitbart_news or breitbart_sections, leaving the agent to infer the boundary.

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 by the sentence explaining that `section` is required and that some hubs aggregate stories, which helps the agent pick a value. But there is no explicit when-to-use-this vs breitbart_news/breitbart_sections guidance and no exclusions.

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