Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

billboard_headlines

Fetch 10 recent headlines from a chosen Billboard section by providing its slug, such as chart-beat, country, or streaming.

Instructions

Get Billboard section headlines. Returns the 10 most recent items from one Billboard section. section is required and takes a slug such as chart-beat, country, rb-hip-hop, streaming or touring. Parent sections such as music and business overlap with their subsections, so one item can appear under several. Items carry title, URL, summary, author and time.

Input Schema

NameRequiredDescriptionDefault
sectionYesBillboard section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.9/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 does well: it discloses the fixed result size (10 items), the returned fields (title, URL, summary, author, time), and the non-obvious duplication behavior where an item can appear under several parent sections. It omits any auth or rate-limit context, keeping it short of a 5.

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?

Four tight sentences, purpose front-loaded, then size, then the required parameter, then a subtle caveat, then the return fields. No sentence restates structured data wastefully and nothing is padded.

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?

No output schema or annotations exist, so the description must cover the return shape, and it names the fields and count. For a single-param, fixed-size feed it is essentially complete; only the absence of any auth/rate context keeps it from a 5.

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% with a full enum of slugs, so the schema already names every valid value. The description adds value beyond that by giving representative examples (chart-beat, country, rb-hip-hop) and explaining the parent/child overlap semantics of section slugs.

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?

Specific verb and resource ('Get Billboard section headlines'), and it immediately quantifies the result ('10 most recent items from one Billboard section'). It does not, however, distinguish itself from close siblings like billboard_news or billboard_sections, so an agent must infer the routing.

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 implied rather than stated: the reader infers this is a per-section recent-items feed. There is no explicit when-to-use-this-vs-alternative guidance pointing to billboard_news or billboard_sections. The overlap note (parent sections share items with subsections) is contextual, not a selection rule.

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