Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

wapo_author

Get a Washington Post staff author's public profile: bio, byline metadata, contact/social links, and recent articles. Provide a people slug or canonical URL, with optional page.

Instructions

Get a Washington Post staff author profile. Returns one Washington Post staff author's public profile: byline metadata, bio, contact/social links, and one page of their recent articles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoCanonical washingtonpost.com/people/<slug>/ URL, optionally with a ?page= query; alternative to slug
pageNo1-based page number; overrides any page number in url
slugNoWashington Post people slug, e.g. adam-taylor

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full disclosure burden. It is transparent about scope ('one Washington Post staff author's public profile') and enumerates the returned content ('byline metadata, bio, contact/social links, and one page of their recent articles'). The verb 'Get' signals read-only behavior, and nothing contradicts the schema or annotations.

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 focused sentences accomplish the job: the first states the operation, the second lists the returned data. No filler, no repetition of schema details, and the most important information is front-loaded.

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?

There is no output schema, so the description appropriately fills that gap by enumerating the returned profile components and recent-articles page. The input parameters are fully explained in the schema. Minor omissions like exact pagination semantics or error behavior are not critical for a simple profile fetch.

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%, so the baseline of 3 applies. The description does not add parameter-level meaning beyond the schema—it only confirms the notion of 'one page' indirectly. The schema already documents url, page, and slug adequately.

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: 'Get a Washington Post staff author profile.' It also enumerates the returned content, making clear this is the author-profile counterpart to siblings like wapo_article, wapo_headlines, and wapo_sections. An agent can distinguish it immediately.

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?

The intended use is implied by 'Get a Washington Post staff author profile' and the returned data, but the description gives no explicit when-to-use or when-not-to-use guidance and names no alternatives. It is adequate context, not explicit routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools