Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

seattletimes_author

Fetch a Seattle Times author's public profile with bio, email, Twitter link, and latest stories. Provide an author slug or URL to get clean JSON data.

Instructions

Get a Seattle Times author profile. Returns one Seattle Times author's public profile: name, bio, newsroom-published email and X/Twitter link when listed, and their most recent stories.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoCanonical seattletimes.com/author/<slug>/ URL; alternative to slug
slugNoAuthor slug, e.g. mike-lindblom

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/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 does state that the operation is a read ('Get') and describes the return contents, including conditional fields ('when listed'). However, it does not mention behavior on invalid/missing slugs, whether both url and slug can be supplied, or any error/rate-limit characteristics.

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 sentence that front-loads the action and resource, then concisely lists the return fields. Every word earns its place with no filler or repetition.

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?

Since there is no output schema, the description appropriately explains the return payload, including conditional fields like email and X/Twitter link. It does not explicitly state that at least one of url or slug should be provided, but the schema documents both parameters well, making this a minor gap.

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%: both url and slug are documented, with url described as an alternative to slug and slug given an example. The description adds no parameter-level detail, so the baseline of 3 applies.

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 uses a specific verb ('Get') and resource ('Seattle Times author profile') and enumerates the returned fields: name, bio, newsroom-published email, X/Twitter link, and recent stories. This clearly distinguishes it from sibling tools like seattletimes_article, seattletimes_news, and seattletimes_headlines.

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 this tool is for retrieving author profiles, which is clear context, but it does not explicitly state when to use it over alternatives such as seattletimes_article or other author-profile tools. No exclusions, prerequisites, or routing guidance are provided.

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