Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

usmagazine_news

Retrieve Us Weekly top stories as structured JSON, including titles, URLs, summaries, authors, and images; photo galleries are excluded.

Instructions

Get Us Weekly top stories. Returns the latest Us Weekly top stories with no parameters. Each item has its title and URL, plus summary, publication time, author and image when the outlet provides them. Only article URLs of the form /<section>/news/<slug>/ appear; photo galleries are left out.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose behavior. It usefully states there are no parameters, lists returned fields, and explains URL filtering that excludes photo galleries. It does not cover pagination, result limits, ordering guarantees beyond 'latest,' or any access constraints, leaving meaningful behavioral gaps for an unannotated read feed.

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 and then adds only useful output/scope details. Slight redundancy between 'top stories' and 'latest ... top stories,' but no filler or tangential content.

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 simple no-parameter feed, the description gives the key return fields and the article-URL filter, which is enough to set expectations without an output schema. It could state approximate item count or pagination, but otherwise it covers the call surface completely.

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?

There are zero parameters and the empty schema is fully self-evident. The description confirms 'no parameters,' which is sufficient; baseline for 0 params is 4.

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 ('Get Us Weekly top stories') and qualifies the feed as latest. It does not explicitly distinguish itself from sibling usmagazine_headlines, but the 'top stories' framing is clear enough to identify the operation.

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 implies use for fetching the latest Us Weekly feed and notes the no-parameter behavior, but it never names when to prefer this over usmagazine_headlines, usmagazine_sections, or usmagazine_article. The only exclusion is content-level (photo galleries), not an alternative-tool routing rule.

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