Crawlora MCP

usatoday_author

Read-only

Fetch a USA Today staff writer's public profile and recent article links from a canonical author URL. Use usatoday_article for one story or usatoday_headlines and usatoday_news for outlet feeds.

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

Input Schema

Name	Required	Description	Default
`url`	Yes	Canonical USA Today staff 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 USA Today staff URL"
```
First observedOct 5, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety/scope profile. The description adds that it returns a profile plus recent article links from a canonical URL, but does not describe return format, pagination of recent links, or rate limits. With annotations providing the safety context, this is a reasonable but not rich addition.

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, front-loaded with the primary capability, second sentence provides routing guidance. No filler or repetition.

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?

For a single-parameter read-only author fetch with an output schema, the description covers purpose, input expectations, and sibling tool routing. Output schema handles return values, and annotations handle safety. Nothing an agent needs 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 coverage is 100% and the single parameter url is fully documented with 'Canonical USA Today staff URL'. The description reinforces the canonical URL requirement but adds no syntax, format, or edge-case guidance 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?

States a specific verb (Fetch), resource (USA Today staff writer's public profile and recent article links), and input (canonical author URL). It also explicitly names sibling tools it is not, distinguishing it from usatoday_article, usatoday_headlines, and usatoday_news.

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?

Directly tells the agent when to use alternatives: use usatoday_article for one story, or usatoday_headlines/ usatoday_news for outlet feeds. The condition selecting each sibling is clear and leaves 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?