Crawlora MCP

thejournal_article

Read-only

Fetch public TheJournal.ie article metadata and body paragraphs from a canonical url; stories are served in full to anonymous readers and are not marked paywalled. Use thejournal_headlines for story lists, thejournal_sections to browse topics, or thejournal_news for the general feed.

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": "thejournal_article"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Canonical TheJournal.ie 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 TheJournal.ie 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?

Annotations already cover readOnlyHint and openWorldHint, so the safety profile is known. The description adds valuable behavior beyond annotations: stories are served in full to anonymous readers and are not marked paywalled. That's exactly the kind of access/coverage context an agent needs before fetching. It doesn't mention rate limits or response shape, but that's minor given the output schema exists.

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 sentences, zero waste. The core action is front-loaded and the routing guidance follows immediately. No filler.

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?

Complete for a single-URL fetch tool: it states what is retrieved, that access is unrestricted (not paywalled), and how it differs from sibling feed/browse tools. An output schema exists so return values needn't be explained. Only minor gap is no mention of error behavior for a bad/invalid URL, but nothing essential is missing.

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?

Only one parameter and schema description coverage is 100%, so the schema already documents 'url' as a canonical TheJournal.ie article URL. The description reinforces 'canonical url' but adds no format or syntax detail beyond the schema. Baseline 3 is correct.

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: 'Fetch public TheJournal.ie article metadata and body paragraphs from a canonical url.' Clearly identifies the site and what is retrieved. It doesn't name a sibling it is not, but the resource is distinctive enough (article vs. headlines/sections/news) to be separable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: 'Use thejournal_headlines for story lists, thejournal_sections to browse topics, or thejournal_news for the general feed.' Names three alternatives and the condition that selects each, leaving nothing to inference.

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?