Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ew_sections

Lists Entertainment Weekly's nine primary-navigation sections, including TV, movies, music, and more, with each slug, display name, and URL for headline queries.

Instructions

Get Entertainment Weekly sections. Lists the nine Entertainment Weekly primary-navigation sections accepted by ew-headlines: tv, movies, music, what-to-watch, binge, celebrity, awardist, books and theater. Each entry has the slug, display name and section url.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so the description carries the burden. It discloses the return shape (slug, name, url) and the fact that the set is a fixed enumeration of nine values, which is the key behavioral fact for a static lookup. It doesn't confirm read-only safety explicitly, but the lookup nature is unambiguous.

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?

Three sentences, front-loaded with purpose, then the enumeration, then the return fields. Enumerating all nine slugs is slightly long but each value earns its place as the tool's core payload.

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 and no parameters, so the description is responsible for return shape and it delivers: slug, name, url. Nothing an agent needs to call and interpret this tool 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?

Zero parameters, so baseline is 4. The description appropriately spends its text on the enumeration values rather than params, and the schema has no parameters to document.

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 (Entertainment Weekly sections), names the exact consumer tool (`ew-headlines`), and enumerates the nine section slugs. An agent can distinguish this from ew_headlines/ew_news without opening any 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 clarifies this lists the sections accepted by `ew-headlines`, which implicitly routes the agent: fetch valid section values here before calling ew_headlines. No explicit 'when-not-to-use' or exclusion statement, but the context is clear.

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