Crawlora MCP

wsj_author

Read-only

Fetch a Wall Street Journal author's profile and recent articles from a public web-archive snapshot. Use wsj_article for one story.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wsj_author"
  }
}

Input Schema

Name	Required	Description	Default
`url`	No	Canonical https://www.wsj.com/news/author/<slug> URL, as an alternative to slug
`slug`	No	WSJ author slug

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.

Changed2 schema fields changedOct 7, 2026
- addedInput schema / properties / slug / description
```
Added value: +"WSJ author slug"
```
- addedInput schema / properties / url / description
```
Added value: +"Canonical https://www.wsj.com/news/author/<slug> URL, as an alternative to slug"
```
First observedOct 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful context beyond that — the data comes from 'a public web-archive snapshot', signaling it is archived rather than live. It doesn't discuss rate limits or freshness lag, so not 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with no filler; the tool's purpose leads and the sibling-routing hint follows. Every clause earns its place.

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?

An output schema exists so return values need no explanation, and annotations cover the safety profile. The description supplies purpose, source characteristic, and sibling routing, leaving only minor gaps like pagination or freshness for this low-complexity two-parameter tool.

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%, so both the url and slug parameters are already documented in the schema (including the 'as an alternative to slug' relationship). The description adds no parameter detail, which is the correct baseline when the schema does the work.

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?

States a specific verb (Fetch), resource (Wall Street Journal author's profile and recent articles), and scope, plus explicitly distinguishes itself from the sibling wsj_article ('for one story'). An agent can route between the two without opening either schema.

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 alternative (wsj_article) and the condition that selects it (single story), giving clear routing. It stops short of stating prerequisites (e.g., that a slug or author URL is required), so it isn't fully explicit, but the when-to-use context is strong.

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?