Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

houston_chronicle_author

Fetch a Houston Chronicle author profile by canonical URL, returning name, job title, biography, image, social links, and recent article cards.

Instructions

Get a Houston Chronicle author profile. Returns a Houston Chronicle author profile by url, a canonical houstonchronicle.com/author/<slug>/ link. The response has the name, job_title, biography, image_url, social profile links in same_as, and recent article cards with title, URL and summary.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Houston Chronicle author URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

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 behavioral burden. It states the operation is a retrieval ('Get') and enumerates the response payload (name, job_title, biography, image_url, same_as, recent article cards), which is valuable because no output schema exists. It omits auth/rate-limit/pagination details, but for a simple read endpoint this is adequate.

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?

Front-loaded with purpose in the first sentence. The first two sentences partially repeat 'author profile' ('Get... Returns...'), which is mildly redundant, but the field list is efficient and no sentence is wasted.

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 one-parameter tool with no output schema, the description covers the operation, input format, and a detailed response shape including nested social links and article cards. Nothing critical is missing for correct invocation.

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 schema already documents the single `url` parameter. The description adds an example canonical pattern, `houstonchronicle.com/author/<slug>/`, but otherwise mirrors the schema's 'Canonical Houston Chronicle author URL' description. Baseline 3 is appropriate when the schema does the heavy lifting.

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 Houston Chronicle author profile.' The resource is specific enough to distinguish it from sibling tools such as houston_chronicle_article, houston_chronicle_news, and other publisher author 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?

No explicit when/when-not guidance or alternatives are provided. The phrase 'by `url`, a canonical `houstonchronicle.com/author/<slug>/` link' implies it is used when a canonical author URL is already known, but it does not tell the agent when to choose this over sibling tools or how to find the URL.

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