Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

usmagazine_headlines

Retrieve recent Us Weekly headlines for a specified section, returning up to 20 items across celebrity, entertainment, sports, and other categories.

Instructions

Get Us Weekly section headlines. Lists recent Us Weekly headlines for one section. section is required and takes celebrity-news, entertainment, sports, shopping, crime-news, stylish, celebrity-moms, celebrity-body, food, reviews, reality-tv or royal-family. Returns up to about 20 items, with photo galleries excluded; reviews holds only a few.

Input Schema

NameRequiredDescriptionDefault
sectionYesUs Weekly RSS section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/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 it does deliver useful behavioral context: roughly 20 returned items, photo galleries excluded, and the caveat that 'reviews' yields only a few. Auth requirements, rate limits, and pagination behavior are unstated, but for a public headline feed the disclosed result-set characteristics cover the main operational surprises.

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 the purpose and scoping constraint before the value list and return caveats. The full enum repetition is mildly redundant against the schema, but nothing else is padding.

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-parameter, no-output-schema tool this is close to complete: the agent learns the required argument, its legal values, and the shape and limits of the result set. Only the distinction from sibling Us Weekly tools remains unaddressed.

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 description coverage is 100% and the enum is fully declared in the schema, so the description's enumeration of section slugs largely duplicates structured data. Requiredness and the accepted values add no syntax or format detail beyond what the schema already provides, making 3 the correct baseline.

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 and resource — 'Lists recent Us Weekly headlines for one section' — so an agent knows exactly what comes back. It does not explicitly distinguish itself from the sibling usmagazine_news or usmagazine_article, so the boundary with those tools must be inferred from their names.

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?

The description names the required parameter and enumerates its accepted values, which implies when the tool is callable, but never states when to prefer it over usmagazine_news, usmagazine_sections, or usmagazine_article. Usage is implied rather than explained, so no exclusions or alternatives are given.

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