Crawlora MCP

mashable_author

Read-only

Fetch a Mashable author's profile and one page of recent article links. Use mashable_article to read one story or mashable_news and mashable_headlines for outlet feeds.

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

Input Schema

Name	Required	Description
`url`	No	Canonical mashable.com/author/<slug> URL; alternative to slug
`page`	No	1-based page number of the article list
`slug`	No	Author slug, e.g. amanda-yeo

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 article list"
```
- addedInput schema / properties / slug / description
```
Added value: +"Author slug, e.g. amanda-yeo"
```
- addedInput schema / properties / url / description
```
Added value: +"Canonical mashable.com/author/<slug> URL; alternative to slug"
```
First observedOct 5, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that the result is exactly one page of article links, clarifying scope and pagination, but says nothing about permissions or freshness. Useful added context beyond annotations, but not exhaustive.

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 filler, with the core behavior front-loaded and the routing guidance second. Every sentence 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 present and full parameter documentation, the description only needs to convey purpose, scope, and alternatives — all of which it does. Nothing an agent needs to call this correctly 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?

Schema description coverage is 100%, with url, slug, and page all documented and the url/slug alternative noted in the schema itself. The description only adds that the article list is paginated to one page, which maps loosely to the page parameter. Baseline 3 is appropriate.

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 verb and resource: 'Fetch a Mashable author's profile and one page of recent article links.' It clearly distinguishes this tool from mashable_article, mashable_news, and mashable_headlines, so an agent can pick it without opening any schema.

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?

It explicitly names the alternatives and the conditions that select them: mashable_article for a single story, mashable_news and mashable_headlines for outlet feeds. This is a rare case of true when-to-use/when-not routing.

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?