Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

thehill_author

Fetch a The Hill author profile by canonical URL to get name, job title, bio, image, and recent articles with categories and links.

Instructions

Get a The Hill author profile. Returns a The Hill author's profile by url, a canonical thehill.com/author/<slug>/ link: name, job title, bio, image URL and recent articles with title, URL, category and category URL. job_title and image_url may be missing, and each article's published_at is relative text such as 10 hours ago, not a timestamp.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical The Hill author URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/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 behavioral burden and does useful work: it warns that `job_title` and `image_url` may be missing and that `published_at` is relative text ('10 hours ago'), not a timestamp. It omits auth needs, rate limits, and how many recent articles are returned.

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 one-line purpose, then the return shape and caveats in a single follow-up sentence. Dense but every clause (fields, missing fields, timestamp quirk) carries information; nothing is filler.

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?

No output schema or annotations, so the description must convey the return shape, and it does: it lists profile fields and article sub-fields plus data quirks. The only gap is not stating how many 'recent articles' come back or whether results are paginated.

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% and the schema already labels the single param 'Canonical The Hill author URL'. The description adds value by giving the concrete format `thehill.com/author/<slug>/`, which helps an agent construct or validate the input.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Get') and resource ('a The Hill author profile'), then enumerates the returned fields (name, job title, bio, image, recent articles), which cleanly separates it from thehill_article/news/headlines siblings. It does not explicitly name an alternative, so it lands just short of the top tier.

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 implied: the tool takes a canonical author URL and returns that author's profile. There is no explicit when-to-use/when-not guidance and no mention of alternatives (e.g. thehill_article for a single story, or how to obtain the author URL in the first place).

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