Crawlora MCP

wapo_author

Read-only

One Washington Post staff author's public profile: byline metadata, bio, contact/social links, 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": "wapo_author"
  }
}

Input Schema

Name	Required	Description
`url`	No	Canonical washingtonpost.com/people/<slug>/ URL, optionally with a ?page= query; alternative to slug
`page`	No	1-based page number; overrides any page number in url
`slug`	No	Washington Post people slug, e.g. adam-taylor

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; overrides any page number in url"

addedInput schema / properties / slug / description

Added value: +"Washington Post people slug, e.g. adam-taylor"

addedInput schema / properties / url / description

Added value: +"Canonical washingtonpost.com/people/<slug>/ URL, optionally with a ?page= query; alternative to slug"

First observedOct 5, 2026

TDQS

A3.6/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, so the safety profile is covered. The description usefully adds that only 'one page' of recent articles is returned, hinting at pagination scope, but says nothing about auth needs, rate limits, or how to page further.

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 whose colon-delimited list of returned data types is entirely informative with no filler. Nothing could be cut without losing content.

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-value detail is not required, and the description adequately signals the resource and its scope ('one page'). It is slightly thin on how the three optional inputs interact, but the schema carries that, so it is close to complete.

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%: url (canonical URL, optionally with ?page=), page (1-based, overrides url), and slug are all documented in the schema. The description adds no parameter meaning beyond that, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific resource ('One Washington Post staff author's public profile') and enumerates its contents (byline metadata, bio, contact/social links, recent articles), so the agent knows exactly what it retrieves. It does not explicitly distinguish itself from the parallel wapo_article/wapo_news siblings or the many other publisher author tools, relying on the name prefix, so it stops short of a 5.

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: fetch a single author profile, and the url/slug inputs signal how to target one. There is no explicit when-to-use/when-not guidance and no named alternative (e.g. 'use wapo_news for latest stories'), so it is only minimally viable.

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?