Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

breitbart_sections

List all 21 Breitbart sections with slugs, names, and URLs to find valid categories for headline filtering.

Instructions

Get Breitbart sections. Lists the 21 Breitbart sections accepted by breitbart-headlines, including politics, economy, border, national-security, the-media, world-news and america250. Each has a slug, a display name and the section's page url. The list was verified on 2026-09-23.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/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 disclose the return shape (slug, display name, page url), the count of items, and a verification date for freshness. It is a read-only listing, so no destructive/auth/rate-limit concerns are implied, but nothing beyond the output fields is explained.

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?

Front-loaded with the core purpose, followed by the accepted sections, a sample of values, and the return fields. Three dense sentences with no filler; the example enumeration is useful but slightly long, keeping it just short of maximal.

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 zero-parameter list tool with no output schema, the description covers what the agent needs: the count, representative values, and the emitted fields (slug, name, url). It leaves only minor gaps such as whether the list is exhaustive/stable and the exact return envelope.

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?

The tool takes zero parameters, so per the scoring baseline this dimension is a 4. The description appropriately spends no effort on parameter syntax and instead documents the response fields an agent will consume.

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 Breitbart sections') and pins the scope to the 21 section slugs accepted by breitbart-headlines, explicitly naming that sibling. An agent can distinguish this from breitbart_headlines/breitbart_news/breitbart_article without opening a schema.

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?

The description makes the calling relationship explicit: this returns the slugs that breitbart-headlines accepts, so an agent knows to call it to discover valid section inputs. It stops short of stating exclusions or a formal when/when-not rule, so it is clear context but not full routing guidance.

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