Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

huffpost_author

Retrieves a HuffPost author or contributor profile by canonical URL, returning name, recent articles, job title, image, biography, and social links when available.

Instructions

Get a HuffPost author profile. Returns a HuffPost author or contributor profile by url, a canonical https://www.huffpost.com/author/<slug> link. The response has the name, recent articles, and, when the profile shows them, job_title, image_url, biography and social_links (platform and URL). Outside contributors often lack most of these optional fields.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical huffpost.com/author/<slug> URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden and largely succeeds: it discloses the return shape (name, recent articles, and optional profile fields) and warns that outside contributors often lack the optional fields, which sets accurate expectations. It does not address error/lookup-failure behavior, but the read-only nature is conveyed by 'Get'.

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 purpose, then return contents and a caveat. Three tight sentences with essentially no filler; the field enumeration earns its place since no output schema exists.

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 describing the returned fields and their optionality is exactly the right compensation. It is thorough for a single-parameter read tool, missing only lookup-failure behavior.

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 url parameter is already documented. The description restates the canonical 'https://www.huffpost.com/author/<slug>' format, adding marginal clarity but no syntax or format detail beyond the schema – baseline 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?

Opens with a specific verb+resource ('Get a HuffPost author profile') and immediately clarifies it returns an author or contributor profile keyed by url. This clearly distinguishes it from sibling content tools like huffpost_article or huffpost_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?

Usage is only implied: by saying the response includes 'recent articles,' it hints you'd use this to see an author's output, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative among the many *_author siblings.

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