Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

chicagotribune_author

Fetch a Chicago Tribune author profile via slug or URL to view name, bio, public email, X handle, and recent articles.

Instructions

Get a Chicago Tribune author profile. Returns one Chicago Tribune author's public profile: name, job title when listed, bio, public email and X/Twitter handle, and their recent articles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoCanonical chicagotribune.com/author/<slug>/ URL; alternative to slug
slugNoAuthor slug, e.g. olivia-olander

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It correctly signals a safe read-only operation ('public profile') and explains the return payload. It does not mention constraints like needing exactly one of url/slug, behavior for unknown authors, or rate limits, but it is not misleading.

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?

The description is a single dense sentence that front-loads the action and resource, then lists the return fields. Every clause earns its place and there is no redundant or vague filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple lookup tool, the returned fields are adequately described, and the schema covers parameter meaning. However, required:[] leaves ambiguity about whether exactly one of url or slug must be supplied, and the absence of an output schema leaves the structure of 'recent articles' unclear.

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?

The input schema already fully documents both parameters, including descriptions and an example slug, so schema coverage is 100%. The description adds no additional parameter-level meaning, so the baseline of 3 is appropriate.

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 Chicago Tribune author profile,' and enumerates exactly what is returned (name, job title, bio, email, X/Twitter handle, recent articles). The Chicago Tribune scoping clearly distinguishes it from sibling author tools for other publications and from chicagotribune_article/headlines/sections.

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 implies when to use it: any task needing a Chicago Tribune author's public profile. However, it does not explicitly name alternatives or state when not to use it, such as pointing users to chicagotribune_article for article content instead.

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