Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

npr_author

Fetch an NPR author profile from a canonical www.npr.org/people URL, returning name, job title, bio, and recent stories with titles, links, summaries, dates, and lead images.

Instructions

Get an NPR author profile. Returns an NPR author profile from a required url in the form https://www.npr.org/people/<id>/<slug>. The response has name, job_title, bio and the recent stories listed under Stories By, each with title, URL, summary, publication date and a lead image where the card has one. Other hosts or paths return a bad-request error.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical www.npr.org author URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses the exact response fields (name, job_title, bio, recent stories with title/URL/summary/date/lead image) and the error behavior for non-NPR hosts or paths. It omits pagination behavior for the stories list and any rate/permission context, so not a full 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, front-loaded with the purpose and scoping constraint, with the return shape last. Slight redundancy between 'Get an NPR author profile' and 'Returns an NPR author profile...' but every sentence otherwise earns its place.

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?

For a single-parameter read tool with no output schema and no annotations, the description covers input format, output fields, and error behavior adequately. It does not address whether the Stories By list is paginated or how many stories are returned, a minor remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema only says 'Canonical www.npr.org author URL', but the description adds real meaning: the concrete URL template https://www.npr.org/people/<id>/<slug> and the fact that other hosts/paths fail. This goes beyond the schema, warranting above the baseline 3.

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?

States a specific verb+resource ('Get an NPR author profile') and details exactly what is returned, so an agent knows the tool fetches a person profile rather than articles or headlines. It does not explicitly differentiate itself from sibling tools such as npr_article or npr_headlines, keeping it just 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 Guidelines2/5

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

There is no when-to-use vs alternatives guidance: nothing says to prefer this over npr_article/npr_headlines, nor when a canonical URL is available. The URL-format constraint and bad-request behavior are input rules, not usage routing guidance.

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