Crawlora MCP

dailymail_author

Read-only

One Daily Mail author's public profile: name, job title, bio, social accounts, and one page of their recent articles.

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

Input Schema

Name	Required	Description	Default
`url`	Yes	Canonical dailymail.com/profile-<id>/<slug>.html URL
`page`	No	1-based page of articles to return; defaults to 1

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 / page / description

Added value: +"1-based page of articles to return; defaults to 1"

addedInput schema / properties / url / description

Added value: +"Canonical dailymail.com/profile-<id>/<slug>.html URL"

First observedOct 5, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations declare readOnlyHint and openWorldHint, covering safety and external fetch. The description adds that the profile includes public bio/social data and only one page of recent articles, which hints at pagination, but it does not add operational details like rate limits or auth behavior beyond what annotations imply.

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?

Single front-loaded sentence that enumerates the return payload without filler. Every element earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema handling return structure, annotations covering safety, and full schema coverage for both parameters, the description supplies the necessary content summary. It omits explicit usage guidance, but that is primarily a separate guidance concern.

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%; both url and page are fully documented in the schema. The description mentions 'one page of their recent articles,' reinforcing the page parameter's meaning, but adds no syntax, format, or default beyond the schema.

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?

The description states a specific resource (Daily Mail author public profile) and enumerates returned fields (name, job title, bio, social accounts, recent articles). It distinguishes itself from sibling dailymail_article/headlines/news by focusing on one author's profile.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is provided, and no alternative sibling (e.g., dailymail_article for individual articles) is named. The agent can infer its purpose but must rely on the tool name alone to choose it over other dailymail_* endpoints.

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?