Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

eonline_headlines

Get E! News section headlines. Returns up to 30 items with title, URL, summary, publication time, author, and image.

Instructions

Get E! News section headlines. Returns up to 30 E! News headlines for one section. section is required and must be one of top_stories, tv, movies, music, celebrities, couples, royals, red_carpet, influencer, style, fashion or shop. Each item has its title, URL, summary, publication time, author and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesE! News section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/5.0
Behavior4/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, and it does disclose the return cap ('up to 30'), the per-section scoping, and the shape of each item (title, URL, summary, publication time, author, image). It omits ordering, freshness window, and any rate-limit/pagination behavior, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first sentence, and the return-shape sentence earns its place given there is no output schema. The inline enumeration of all twelve section slugs is somewhat redundant with the schema enum but not seriously wasteful.

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 one-parameter, no-output-schema, no-annotation tool, the description covers purpose, the required parameter, valid values, the result cap, and the fields returned. That is close to complete; only freshness/ordering and error conditions are unstated.

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% with a full enum, so the schema already documents the single parameter. The description only restates that `section` is required and re-lists the same enum values, adding no new format or scoping semantics beyond the structured field.

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 E! News section headlines') and scopes it to a single section, which implicitly separates it from eonline_news (unscoped news listing) and eonline_sections (section catalog). However, it never explicitly names or contrasts those siblings, so an agent must infer the boundary.

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 by the required `section` parameter and its enumerated values, so an agent can tell the tool is for pulling headlines from one channel. There is no explicit when-to-use/when-not wording and no pointer to eonline_news, eonline_article, or eonline_sections as alternatives.

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