Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

thedailybeast_sections

List The Daily Beast sections accepted by the headlines endpoint, covering top-level categories and child sub-sections with slug, name, and URL.

Instructions

Get The Daily Beast sections. Lists the sections of The Daily Beast that the headlines endpoint accepts, both top-level categories such as politics and world and child sub-sections such as politics/opinion and world/middle-east. Each entry has a slug, a display name and the section url.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.4/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 delivers: it discloses that the result is a lookup list of accepted values, describes each entry's fields (`slug`, display `name`, `url`), and shows the slug format including nested paths. It omits any note on whether the list is exhaustive or static, but there is no misleading claim.

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: the purpose first, then the scope distinction with concrete examples, then the return shape. Every sentence earns its place and the most important routing information is front-loaded.

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?

There is no output schema, so the description appropriately compensates by enumerating the returned fields and giving value examples. What remains missing is an explicit pointer to the sibling headlines tool by name, which would fully close the loop for an agent deciding how to use the slugs.

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 the baseline is 4. There are no inputs whose semantics need explaining, and the description correctly adds no parameter discussion.

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 The Daily Beast sections') and immediately clarifies the scope: the section slugs accepted by the headlines endpoint. The examples of top-level vs. child sections (`politics` vs `politics/opinion`) make the tool's output unambiguous against the many sibling `*_sections` and `*_headlines` tools.

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 ties the tool to a concrete use case: it lists 'the sections of The Daily Beast that the headlines endpoint accepts', which tells the agent this is the discovery step before calling the headlines tool. It does not explicitly name the sibling tool `thedailybeast_headlines` or state any exclusions, so it falls short of a full 5.

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