Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

latimes_author

Retrieve a Los Angeles Times author profile from a canonical latimes.com/people URL, returning name, job title, bio, email, image, social accounts, and recent articles.

Instructions

Get a Los Angeles Times author profile. Returns a Los Angeles Times author profile by url, a canonical https://www.latimes.com/people/<slug> link; other hosts or paths return a bad-request error. The response has the name, job_title, bio, email, image_url, social_accounts and recent articles with title, URL, summary, publication time and lead image. Accounts the page does not list are absent.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Los Angeles Times author URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.1/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 burden and does well: it discloses the error mode for non-canonical URLs, enumerates the returned fields, and notes the negative behavior that unlisted accounts are absent. It omits rate limits or auth, but for a public profile fetch this is solid disclosure.

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 the core purpose, then constraints, then return shape. Every sentence earns its place, though the long enumeration of response fields is slightly list-like rather than prose-efficient.

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?

With no output schema and a single required param, the description covers purpose, input constraints, error behavior, and the returned field set, which is enough for correct invocation. It is close to complete for a simple fetch tool.

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 the single parameter is already documented, but the description adds real value by giving the canonical URL pattern (https://www.latimes.com/people/<slug>) and the failure condition for off-host URLs, going beyond the schema's generic "Canonical Los Angeles Times author URL".

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 opens with a specific verb+resource ("Get a Los Angeles Times author profile") and scopes it to the LA Times, which cleanly distinguishes it from the many other *_author siblings (vice_author, nymag_author, etc.). An agent can identify the tool without opening the schema.

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?

It states the valid input shape (canonical /people/<slug> URL) and that other hosts or paths error out, which is useful guidance. However, it never states when to choose this tool over alternatives like latimes_article or latimes_headlines, nor any prerequisites, so usage is only implied.

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