Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

marketwatch_article

Fetch a MarketWatch article by canonical URL, returning title, authors, timestamps, body paragraphs, and a paywalled flag; blocked links may fail.

Instructions

Get MarketWatch article content. Returns a MarketWatch article by url, a canonical HTTPS article link. The response has the title, description, section, authors, lead image, publish and update times, body paragraphs and a paywalled flag. Subscriber-only or blocked articles return an upstream error, so some URLs may fail.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical MarketWatch article URL

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 behavioral burden and does it well: it enumerates the returned fields (title, section, authors, paragraphs, paywalled flag) and, importantly, warns that subscriber-only or blocked articles return an upstream error so some URLs will fail. It omits auth requirements and rate limits, which keeps it from a 5.

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 front-loaded sentences, each earning its place: what it does, what it returns, and how it can fail. No redundancy or filler, though it could be tightened slightly.

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 one-parameter tool with no output schema, the description must describe return values and it does so explicitly (title, description, section, authors, lead image, times, paragraphs, paywalled flag). Pairing that with the upstream-error caveat makes it largely complete, with the only gap being authentication/environment notes.

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%, so the schema already documents the single `url` parameter, and the baseline is 3. The description only adds that the URL is a canonical HTTPS link, a marginal detail beyond the schema's "Canonical MarketWatch 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?

States a specific verb and resource ("Get MarketWatch article content") and scopes it to a single article by URL, which clearly separates it from the list-style siblings marketwatch_headlines, marketwatch_news and marketwatch_sections. It does not explicitly name those alternatives, so it falls short of full sibling differentiation.

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 only implied: the requirement of a canonical article URL signals this is a detail-fetch tool used after a headlines/news lookup, but the description never says when to choose it over marketwatch_headlines or marketwatch_news. No explicit when-to-use or when-not-to-use guidance is 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