Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

theblaze_headlines

Fetch up to 30 recent Blaze Media section headlines by passing an exact slug; returns titles, URLs, summaries, authors, and images when available.

Instructions

Get Blaze Media section headlines. Returns up to 30 recent stories from one TheBlaze (Blaze Media) section. section is required, case-sensitive and must match exactly, for example news, columns/opinion, lifestyle/men, tech or a show such as shows/relatable. Other values are rejected. Items have a title and URL, plus summary, author, publication time and image when the outlet provides them.

Input Schema

NameRequiredDescriptionDefault
sectionYesExact Blaze Media section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

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 burden and discloses meaningful behavior: return volume (up to 30 recent stories), available item fields, and strict section validation. It does not discuss authentication or rate limits, but for an apparently read-only headlines endpoint that is a minor omission.

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?

The description is front-loaded with purpose and scope, then moves to parameter constraints and return fields. Every sentence adds concrete value without repetition.

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?

For a simple one-parameter tool with no output schema and no annotations, the description covers the essential call behavior, validation rules, and enough return-field detail for an agent to know what to expect.

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 enum already enumerates valid sections, so the baseline is 3. The description adds useful meaning by explaining case sensitivity, exact matching, rejection of other values, and practical examples.

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?

The description states a specific verb and resource: "Get Blaze Media section headlines" and clarifies it returns up to 30 recent stories from one section. This distinguishes it from article-level siblings by making the headline/section scope explicit.

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?

It explains that `section` is required, case-sensitive, must match exactly, and that other values are rejected, with concrete examples. It does not explicitly compare this tool to nearby siblings such as theblaze_news or theblaze_article, so it stops short of full when-to-use 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