Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

eonline_author

Retrieve an E! News writer's name and articles from an author page URL, with pagination for older entries. Use it to collect bylines and article lists without bio or photos.

Instructions

Get an E! News author page. Returns an E! News writer's name and the articles on their author page, about 45 per page, for a url like https://www.eonline.com/authors/natalie-finn (add /page/<n> for older ones). There is no biography or photo. published_at is the page's own text, such as 18 minutes ago, not a timestamp.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical E! News author 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 so well: it discloses ~45 articles per page, the pagination mechanism, the absence of biography/photo, and that published_at is relative page text rather than a timestamp. It omits auth/rate-limit behavior, though that is minor for a public read tool.

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 tight sentences, front-loaded with the purpose, then return contents, then edge-case quirks. Every sentence adds information with no filler.

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?

No output schema exists, so the description must describe returns, and it does: name, articles, per-page count, pagination, and the published_at format quirk. An agent has everything needed to call and interpret the result.

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 schema already labels url as 'Canonical E! News author URL', so baseline is 3. The description adds real value beyond the schema by showing a full example URL and the /page/<n> suffix convention.

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 author page'), then enumerates what is returned (name + articles). This clearly distinguishes it from siblings such as eonline_article, eonline_news, and eonline_sections.

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?

Gives a concrete URL format and explains the pagination convention ('add /page/<n> for older ones'), which effectively tells the agent how to invoke it and reach older content. It does not, however, explicitly state when to prefer or avoid this tool versus sibling news/article tools.

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