Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

thedailybeast_news

Retrieve current top stories from The Daily Beast as structured JSON with titles, URLs, summaries, authors, timestamps, and lead images for a front-page view.

Instructions

Get The Daily Beast top stories. Returns the current top stories from The Daily Beast. It takes no parameters. Each item has its title, URL, summary, publication time, author and lead image, so it is a quick front-page view; use the headlines endpoint with a section slug for one category.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the full burden and handles it well: it states that the tool takes no parameters and enumerates the returned fields (title, URL, summary, publication time, author, lead image). It omits auth/rate-limit behavior, but for a read-only front-page snapshot that is a minor gap.

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 action, then the alternative route at the end where it belongs. Slightly padded by restating 'top stories' in both the first and second sentence, so not maximally tight.

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 no-param, no-output-schema tool, the description covers both the invocation (no params) and the return shape (item fields), plus routing to the sibling endpoint. Nothing essential is missing for correct selection or invocation.

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?

Zero parameters, so the baseline is 4. The description's explicit 'It takes no parameters' correctly reinforces the empty schema and prevents an agent from hunting for required inputs.

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 top stories'), and explicitly sets scope apart from the category-specific 'headlines endpoint'. The first two sentences are near-redundant, but the purpose is unambiguous and distinguishable from thedailybeast_headlines/sections siblings.

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?

Provides a clear use case ('quick front-page view') and names the alternative route for a different need ('use the headlines endpoint with a `section` slug for one category'). No exclusions beyond that, but the when-to-use and the alternative are explicit.

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