Crawlora MCP

thejournal_author

Read-only

Fetch the first page of a TheJournal.ie author's public archive, including author name, numeric ID, and recent article links. Use thejournal_article with one story URL when you need its content.

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

Input Schema

Name	Required	Description	Default
`url`	No	Canonical thejournal.ie/author/<slug>/ URL, optionally with the numeric author id; alternative to slug
`slug`	No	Author slug, e.g. ottoline-spearman

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: +"Author slug, e.g. ottoline-spearman"

addedInput schema / properties / url / description

Added value: +"Canonical thejournal.ie/author/<slug>/ URL, optionally with the numeric author id; alternative to slug"

First observedOct 5, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/openWorldHint, so the bar is lower; the description adds that only the first page is returned (implying no pagination/full-archive traversal) and enumerates what comes back. It stops short of stating rate limits or failure modes, but adds real value beyond the annotations.

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?

Two tight, front-loaded sentences with no filler. The field enumeration slightly duplicates what the output schema already conveys, but the description remains short and readable.

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?

With an output schema present, return values need not be explained, and the description covers scope and the cross-tool routing decision. Minor omissions (no note on pagination limits beyond 'first page', no slug/URL guidance) keep it from a 5.

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% and the two parameters (url, slug) are fully documented there, including that they are alternatives. The description never mentions them, so the baseline 3 applies since the schema carries the parameter burden.

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) and resource (a TheJournal.ie author's public archive), plus scope ('first page') and the fields returned. It also names the sibling it is not, so an agent can distinguish it from thejournal_article without opening a 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?

Explicitly routes content retrieval to thejournal_article with one story URL, giving a clear when-to-use-this-instead signal. It does not cover the relationship to thejournal_headlines/news/sections, but the core boundary is stated.

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?