Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

hollywoodreporter_news

Fetch The Hollywood Reporter's current entertainment-industry stories from its home feed. Returns titles, URLs, summaries, authors, publication times, and images when available.

Instructions

Get The Hollywood Reporter top stories. Returns The Hollywood Reporter's current top entertainment-industry stories from its home feed, with no parameters. Each item has its title and URL, plus summary, author, publication time and image when the outlet provides them.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

B3.4/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 full burden. It does disclose the shape of each returned item (title, URL, summary, author, publication time, image) and states that fields are conditional ('when the outlet provides them'), which is useful. It omits the number of items returned, freshness/refetch behavior, and does not explicitly state that the call is a read-only, side-effect-free operation.

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, front-loaded with the outlet and resource, then the return contents. The first two sentences partially restate the same idea ('top stories' / 'current top entertainment-industry stories from its home feed'), so a small amount of redundancy remains.

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?

With no output schema and no annotations, the description picks up both burdens and does so reasonably: it names the source feed, the absence of inputs, and the fields in each item. What is missing is any signal resolving it against the sibling headlines/news/article tools for the same outlet.

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 there is nothing for the description to disambiguate beyond confirming it, which it does ('with no parameters'). Baseline 4 applies for a parameterless tool.

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 Hollywood Reporter top stories') and scopes it to the outlet's home feed, which tells an agent what it returns. It does not, however, distinguish itself from the closely named sibling hollywoodreporter_headlines, leaving the agent to guess which one to call.

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?

There is no when-to-use or when-not-to-use guidance. The phrase 'with no parameters' is a structural fact rather than a routing cue, and the presence of hollywoodreporter_headlines, hollywoodreporter_article, hollywoodreporter_sections and hollywoodreporter_author among the siblings makes the missing differentiation costly.

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