Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ew_headlines

Get Entertainment Weekly headlines for a chosen section like TV, movies, music, or books; each result includes title, URL, and image when shown.

Instructions

Get Entertainment Weekly section headlines. Returns the latest Entertainment Weekly headlines for one section. section is required and must be one of tv, movies, music, what-to-watch, binge, celebrity, awardist, books or theater. Each item has its title and URL, plus an image when the card shows one.

Input Schema

NameRequiredDescriptionDefault
sectionYesEntertainment Weekly section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.5/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 behavioral burden. It usefully discloses that results are the latest headlines and that each item contains a title, URL, and sometimes an image, but it does not mention ordering, pagination, limits, or other operational behavior.

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?

The description is front-loaded and appropriately short for a simple headlines tool. The enum repetition is somewhat redundant with the schema, but it does not obstruct readability.

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 simple one-parameter headlines tool with no output schema, the description is nearly complete: it names the resource, specifies the required section, and explains the shape of returned items. Minor operational details such as result limits or ordering are omitted but not critical.

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 coverage is 100% and the single parameter is fully documented by the schema, including its enum. The description repeats the same enum and requirement, adding little meaning beyond what the schema already provides, so the baseline score of 3 applies.

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?

The description states a specific verb and resource: getting the latest Entertainment Weekly headlines for a section. It is clear what the tool returns, though it does not explicitly differentiate itself from nearby siblings such as ew_news or ew_article.

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?

The intended use is strongly implied by 'section headlines' and the required section enum, but there is no explicit guidance on when to choose this tool over alternatives such as ew_news, ew_article, or ew_sections.

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