Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

denverpost_author

Fetch a Denver Post author's profile and first-page articles by slug or author URL, returning name, title, bio, contact handles, and article details.

Instructions

Get a Denver Post author archive. Returns a Denver Post author's profile and the articles on the first page of their archive. Give exactly one of slug (for example aldo-svaldi) or url (a denverpost.com/author// link). The profile has name, job title, bio, email and Twitter handle where the page shows them; each article has a title, URL, summary and publication time.

Input Schema

NameRequiredDescriptionDefault
urlNoCanonical denverpost.com/author/<slug>/ URL; alternative to slug
slugNoAuthor slug, e.g. aldo-svaldi

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does so reasonably: it discloses the read-only GET-like nature implicitly and enumerates the returned fields for both profile and articles. It does not cover failure behavior (invalid slug, missing author) or whether further pages of the archive are reachable, which is the remaining gap.

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?

Four tight sentences, front-loaded with purpose and return contents before parameter rules. No filler, no repetition of the tool name, and each sentence contributes information the agent can act on.

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 must describe returns, and it does so thoroughly for both profile and article objects. It is nearly complete for a simple archive fetcher, with only pagination scope and error behavior left unstated.

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%, so baseline is 3, but the description adds real value beyond the schema: the mutual-exclusivity rule ('exactly one of'), a concrete slug example ('aldo-svaldi'), and the accepted URL shape ('denverpost.com/author/<slug>/'). That is meaningful semantics the schema alone does not spell out.

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 and resource ('Get a Denver Post author archive') and immediately details exactly what is returned: the author profile plus the first page of their articles. This cleanly separates it from the sibling denverpost_article, denverpost_headlines and denverpost_news tools.

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 description tells the agent how to call it ('give exactly one of slug or url') but never states when to choose this tool over the sibling Denver Post tools operating on articles/headlines/sections. The phrase 'first page of their archive' implies a limiting condition but the agent must infer it.

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