Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

eonline_article

Retrieve complete E! News article content using its canonical URL. Extract the title, body paragraphs, publish time, and section data for specific news stories.

Instructions

Get E! News article content. Returns one E! News article by its url, in the form https://www.eonline.com/news/<numeric id>/<slug>. The response has the title, description, publish time, byline, lead image, body paragraphs and section, which is the article's first tag. Photo galleries, videos and show pages are rejected; an unknown id returns not-found.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical E! News article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.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 full burden and does well: it enumerates the returned fields (title, description, publish time, byline, lead image, body paragraphs, section) and discloses failure behavior (unsupported page types rejected, unknown id returns not-found). It omits auth/rate-limit context, but for a read-only fetch that gap is minor.

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 sentences, front-loaded with the core action, then input format, then response/error behavior. No filler and every sentence contributes distinct information.

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 fetch tool with no output schema and no annotations, the description supplies input format, response shape, and rejection/not-found behavior. Nothing an agent needs 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 single param is documented as 'Canonical E! News article URL', so baseline is 3. The description adds real value beyond the schema by spelling out the exact URL template 'https://www.eonline.com/news/<numeric id>/<slug>', which tells the agent what a valid identifier actually looks like.

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 (Get) and resource (E! News article content) and pins the scope to exactly one article retrieved by url. This cleanly separates it from siblings like eonline_news, eonline_headlines, eonline_sections and eonline_author, which an agent could otherwise confuse with it.

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

Usage Guidelines4/5

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

The description gives the required url shape and states that photo galleries, videos and show pages are rejected, which is effective when-not guidance. It does not, however, explicitly route the agent to a sibling (e.g. use eonline_news to discover article URLs first), so the usage context is clear but not fully comparative.

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