Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

eonline_sections

List the 12 E! News sections accepted by eonline-headlines, including slug, name, and feed URL, so you can pick valid categories before querying.

Instructions

Get E! News sections. Lists the 12 E! News sections accepted by eonline-headlines, from top_stories, tv and movies to royals, fashion and shop. Each entry has the slug, name and feed url. The list is curated from the main navigation hubs and major tag feeds, not every tag.

Input Schema

NameRequiredDescriptionDefault

No arguments

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 discloses the return fields (slug, name, feed url) despite no output schema, and it sets a scope caveat that the list is curated from navigation hubs and major tags, 'not every tag.' Auth and rate-limit behavior are not covered, 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.

Conciseness5/5

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

Three sentences, front-loaded with purpose, then the sibling relationship, then the return shape and scope caveat. Every sentence adds distinct value 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?

For a parameterless listing tool with no output schema, the description supplies everything needed: what it returns, the fields per entry, the count, and the caveat about non-exhaustive coverage.

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 to disambiguate; the schema is trivially complete. Baseline of 4 applies for a no-param tool, and the description adds field-level detail on the returned entries.

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/Lists) and resource (E! News sections), and explicitly distinguishes itself from the sibling eonline-headlines by naming it and defining the relationship. An agent can tell exactly what this returns without opening a schema.

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?

It frames itself as supporting `eonline-headlines` by noting the listed sections are the ones that tool accepts, which implies calling this first to discover valid values. There is no explicit when-not guidance, but the routing context is clear and correct.

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