Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

newsweek_headlines

Retrieve recent Newsweek headlines for a specified section by passing its slug, so you can monitor politics, business, technology, or other coverage.

Instructions

Get Newsweek section headlines. Returns recent Newsweek stories for one section. section is required and takes one of 21 slugs, such as politics, fact-check, better-planet, personal-finance or my-turn. Each item has a title and URL, and may include summary, author, publication time and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesNewsweek section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the return shape (each item has title and URL, may include summary, author, publication time and image), but says nothing about its read-only nature, auth requirements, result count/limits, or freshness beyond 'recent'.

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?

Front-loaded with the core action, then the scoping rule, then the return shape. Roughly four compact sentences with little waste, though the parameter examples and the output list slightly overlap with schema information.

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 single-enum, read-only list tool the description covers the action, the required parameter, and the item shape well, and no output schema exists that would obviate that. The main gap is the absence of any routing guidance against the many sibling headline/news tools.

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 coverage is 100% and the enum is fully documented, so the baseline is 3. The description adds illustrative examples ('politics', 'fact-check', 'better-planet') and confirms the count (21 slugs), which lightly reinforces but does not extend the schema.

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+resource ('Get Newsweek section headlines') and scope ('recent Newsweek stories for one section'), which sets it apart from a site-wide feed. However, it never names or differentiates from the closely related siblings like newsweek_news or newsweek_sections, so an agent must infer the distinction.

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: fetch headlines for a single section. There is no explicit statement of when to use this versus newsweek_news, newsweek_sections, or newsweek_article, and no exclusions or prerequisites beyond 'section is required'.

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