Retrieve a HuffPost author or contributor's public profile—name, title, bio, headshot, social links, and recent articles—from a canonical author URL.
Get a HuffPost author profile. Returns one HuffPost author or contributor's public profile: name, job title, headshot, biography, social links, and their recent articles.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Canonical huffpost.com/author/<slug> URL |
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the burden of behavioral disclosure. It makes the read-only nature clear through 'Get' and labels the data as a 'public profile,' while also disclosing the specific profile fields and the inclusion of recent articles. It does not mention pagination or potential limitations, but the operation is simple and well-scoped.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no filler. The first sentence front-loads the action and resource, and the second efficiently enumerates the return fields. Every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter, low-complexity fetch tool, the description is nearly complete. It identifies the input URL format via the schema and describes the output content since no output schema exists. The only minor gap is specifying how many recent articles are returned.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the parameter is well-documented as a canonical huffpost.com/author/<slug> URL. The description adds no further parameter detail, but given full schema coverage, the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb and resource ('Get a HuffPost author profile'), and enumerates the returned content: name, job title, headshot, biography, social links, and recent articles. This clearly distinguishes it from sister 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.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool is for retrieving an author/contributor profile and its associated recent articles, but it does not explicitly state when to prefer this over alternatives or mention exclusions. There is no routing guidance to sibling tools, so the usage context is only inferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.