Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

thedailybeast_headlines

Retrieve current stories from a specified The Daily Beast section using a slug, returning title, URL, summary, author, publication time, image and type.

Instructions

Get The Daily Beast section headlines. Returns the current headlines of one The Daily Beast section. section is required and takes a slug such as politics, politics/opinion, obsessed/reviews, scouted/home or world/china. Each item can carry its title, URL, summary, author, publication time, lead image and type, and the response echoes the section.

Input Schema

NameRequiredDescriptionDefault
sectionYesThe Daily Beast section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.5/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 load. It discloses the return shape well (title, URL, summary, author, publication time, lead image, type) and the section echo, but says nothing about item count, pagination, freshness, or rate limits for a feed endpoint where those matter.

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?

Three front-loaded sentences with the purpose stated first, then the parameter, then the return contents. There is mild redundancy between 'Get ... headlines' and 'Returns the current headlines of one ... section,' but no filler overall.

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-parameter read tool with no output schema and no annotations, the definition covers purpose, the required input, and the fields each returned item can carry. The only real gap is feed mechanics (number of items, paging), which is minor here.

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% and the single parameter is a fully enumerated slug list, so the schema already does the heavy lifting; baseline is 3. The description's slug examples ('politics/opinion', 'obsessed/reviews') restate values already present in the enum, adding marginal meaning beyond the schema.

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 The Daily Beast section headlines') and scopes it to 'one The Daily Beast section,' which separates it from the brand-level siblings thedailybeast_news and thedailybeast_sections. It does not explicitly contrast with thedailybeast_article, but the resource is unambiguous.

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 only implied: the description notes the section is required and gives slug examples, from which an agent infers this is for pulling a single section's feed. It never states when to prefer this over thedailybeast_news or thedailybeast_sections, and offers no exclusions or prerequisites.

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