Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

usmagazine_article

Fetch a Us Weekly article by its canonical URL and return clean JSON with title, authors, publish/update times, lead image, and body paragraphs.

Instructions

Get Us Weekly article content. Returns one Us Weekly article by its canonical url, in the form /<section>/news/<slug>/. The response has the title, description, published and updated times, section, authors, lead image and the body paragraphs, without sub-headings or embeds. Photo-gallery URLs and non-article pages return a 400 error.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Us Weekly article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden and does well: it discloses the returned fields, notes that the body paragraphs exclude sub-headings and embeds, and explains the 400 error for non-article and photo-gallery URLs. It does not cover authentication or rate limits, but for this public article-fetching tool the disclosed behavior is sufficient.

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?

The description is front-loaded with the core purpose and then adds only useful details about URL format, response content, and error conditions. Every sentence earns its place with no redundancy.

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 single-parameter article retrieval tool with no output schema and no annotations, the description supplies the essential context: what it returns, what the body excludes, the canonical URL pattern, and the failure case for non-article URLs. Nothing critical is missing for correct invocation.

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 schema already documents the single `url` parameter at 100% coverage, so the baseline is 3. The description adds valuable meaning by specifying the expected canonical URL shape `/<section>/news/<slug>/`, which helps the agent construct or validate input beyond the schema's generic 'Canonical Us Weekly article URL'.

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?

The description states a specific verb and resource: 'Get Us Weekly article content' and 'Returns one Us Weekly article by its canonical url.' It clearly distinguishes article retrieval from generic site content, though it does not explicitly name sibling tools such as usmagazine_headlines or usmagazine_news.

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?

The description gives clear usage context by specifying the canonical URL form `/<section>/news/<slug>/` and by stating that photo-gallery URLs and non-article pages return a 400 error. It does not explicitly compare against sibling tools, but the practical boundaries are 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