Crawlora MCP

wsj_article

Read-only

Fetch a Wall Street Journal article's title, byline, publication time, word count, and body from a public web-archive snapshot. Use wsj_author to find a writer's profile and recent stories.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "wsj_article"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Canonical WSJ article URL

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026
- addedInput schema / properties / url / description
```
Added value: +"Canonical WSJ article URL"
```
First observedOct 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Adds meaningful context beyond the annotations: the content comes 'from a public web-archive snapshot', which tells the agent the data is archived rather than live and is publicly sourced. Annotations cover readOnly/openWorld safety, so this is the useful extra layer, though failure behavior (article not archived) is unstated.

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?

Two tight sentences, zero waste, with the core capability front-loaded before the sibling pointer. Nothing is redundant or padded.

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?

Annotations and an output schema mean the safety profile and return shape are already covered, and the description goes further by naming the fields and the archive source. For a one-parameter fetch this is essentially complete, with only edge-case behavior left implicit.

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% ('Canonical WSJ article URL'), so the schema already documents the sole parameter. The description only reinforces that an article URL is needed without adding format or canonicalization detail beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb 'Fetch' plus a named resource ('a Wall Street Journal article') and an explicit enumeration of the returned fields (title, byline, publication time, word count, body). It is immediately distinguishable from the sibling wsj_author, which the description itself references.

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?

Names the sibling wsj_author and its domain ('writer's profile and recent stories'), giving a clear routing signal, and the required url parameter implies the calling context is 'you already have an article URL'. However it never states when NOT to use this or what to do if the archive lacks the piece.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?