Crawlora MCP

walesonline_author

Read-only

One WalesOnline author's public profile (name, plus job title, bio, email and X/Twitter handle when listed) and one page of their recent articles.

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

Input Schema

Name	Required	Description
`url`	No	Canonical walesonline.co.uk/authors/<slug>/ URL; alternative to slug
`page`	No	1-based page number of the author's article list (1 to 100); overrides any pageNumber in url
`slug`	No	Author slug, e.g. rahaf-ali

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.

Changed3 schema fields changedOct 7, 2026

addedInput schema / properties / page / description

Added value: +"1-based page number of the author's article list (1 to 100); overrides any pageNumber in url"

addedInput schema / properties / slug / description
```
Added value: +"Author slug, e.g. rahaf-ali"
```

addedInput schema / properties / url / description

Added value: +"Canonical walesonline.co.uk/authors/<slug>/ URL; alternative to slug"

First observedOct 5, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), so the bar is lower. The description usefully adds that the profile is public and that fields like job title, bio, email, and X handle appear only 'when listed,' but offers nothing on pagination behavior beyond the schema.

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?

A single front-loaded sentence that packs the resource, the returned fields, and the pagination scope with zero waste.

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 the resource and field caveats ('when listed'). Only minor usage context is missing, which keeps it short of a full 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 every parameter (url, page, slug) is documented in the schema, including the url-vs-slug alternative and the page override. The description adds no parameter meaning beyond that, so 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?

States a specific resource (one author's public profile plus one page of their recent articles) and enumerates the fields returned. It clearly distinguishes itself from siblings like walesonline_article, walesonline_headlines, and walesonline_sections without the agent needing to open schemas.

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 implied by the description (fetch a specific author's profile and recent work), but there is no explicit when-to-use guidance, no named alternative for fetching individual articles, and no note on how to obtain a valid slug. Guidance stays at the implied level.

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?