Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

hollywoodreporter_headlines

Fetch headlines from The Hollywood Reporter for a chosen section slug, returning titles, URLs, summaries, authors, times, and images when available.

Instructions

Get The Hollywood Reporter section headlines. Returns recent Hollywood Reporter headlines for one section or editorial vertical. section is required and takes one of 37 slugs such as movie-reviews, tv-news, music-industry-news, awards, heat-vision or thr-esq. Each item has its title and URL, plus summary, author, publication time and image when the outlet provides them.

Input Schema

NameRequiredDescriptionDefault
sectionYesHollywood Reporter section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose the return shape: each item includes title, URL, and optionally summary, author, publication time, and image. It does not mention pagination, ordering, or list size limits, but for a simple read-only headline tool this is substantial disclosure beyond the bare schema.

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 sentences, each earning its place: purpose first, parameter constraints second, return details third. No filler or repetition that would waste the agent's attention.

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, no-output-schema tool, the description covers purpose, required input with examples, and return fields. Minor gaps remain around pagination and ordering, but the essential call information is present.

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 description coverage is 100%, so the enum and required status already document the sole parameter. The description repeats that `section` is required and takes one of 37 slugs and gives examples, which is helpful context but largely redundant with the enum.

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 ('Get') and resource ('Hollywood Reporter section headlines') and clarifies it returns headlines for one section or editorial vertical. It is clear on its own but does not explicitly distinguish itself from siblings like hollywoodreporter_news or hollywoodreporter_article.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides no explicit when-to-use guidance or alternatives. It implies the tool is for section headlines, but never says when to choose it over hollywoodreporter_news, hollywoodreporter_sections, or hollywoodreporter_article.

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