Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

variety_headlines

Fetch fresh entertainment headlines for one vertical by supplying a required section slug such as film, music, or tv. Returns title, URL, summary, author, publish time, and image when available.

Instructions

Get Variety section headlines. Lists fresh Variety headlines for one vertical. section is required and takes a slug such as film, music, tv, biz, awards, gaming, global, legit or vip; variety-sections lists all 24. Each item has its title and URL, plus summary, author, publication time and image when the outlet provides them.

Input Schema

NameRequiredDescriptionDefault
sectionYesVariety vertical slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the disclosure burden. It helpfully describes what each returned item contains (title, URL, summary, author, publication time and image when available), which adds real behavioral value, but says nothing about auth needs, rate limits, or freshness/pagination behavior.

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 front-loaded sentences with no filler: purpose, required parameter with examples and an alternative tool, then return shape. Every sentence earns its place.

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 single-param, no-output-schema headlines tool this covers everything needed: what it returns, which parameter is required, and where to enumerate valid slugs. Nothing an agent needs in order to call it correctly is missing.

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 lists all 24 slugs, so the schema does the heavy lifting (baseline 3). The description goes further by naming representative slugs, restating that `section` is required, and cross-referencing `variety-sections` as the authoritative enumerator, which adds meaning beyond the bare 'Variety vertical slug' schema note.

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/list Variety section headlines) scoped to one vertical, and implicitly routes to `variety-sections` for the full list. An agent can distinguish it from the many sibling `*_headlines` tools because it names the outlet and the section-scoped behavior.

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?

Mentions that `variety-sections` lists all 24 slugs and that a section is required, which implies how to use it. However, it does not state when to prefer this over `variety_news` or `variety_article`, so the headline-vs-news distinction is left to inference.

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