Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

townhall_author

Retrieve a Townhall author profile by slug or canonical URL. Returns name, photo, bio, X link, and first page of archive with story sections and VIP flags; unknown authors return not-found.

Instructions

Get a Townhall author profile. Returns a Townhall author profile by slug (such as amy-curtis) or by an author url; exactly one is required. The response has the name, photo, bio, X profile link and the first page of the author's archive, about 50 stories, each with its section label and a vip flag. Unknown authors return a not-found error.

Input Schema

NameRequiredDescriptionDefault
urlNoCanonical townhall.com/author/<slug> URL; alternative to slug
slugNoAuthor slug, e.g. amy-curtis

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 well: it discloses the response contents (name, photo, bio, X link, first ~50 archive stories with section label and vip flag) and the error behavior for unknown authors. It omits auth/rate-limit details and says nothing about paginating beyond the first page, which keeps it from a 5.

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?

Three tight sentences, front-loaded with the purpose, then inputs, then return shape and error case. Every sentence earns its place with no redundancy.

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 and no annotations exist, so the description must explain returns and behavior; it does both, including the not-found case. It is nearly complete for a simple read tool, missing only pagination/auth notes.

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 baseline is 3, but the description adds genuine value by stating the mutual-exclusion rule ('exactly one is required') and giving an example slug, which the schema does not encode as a constraint.

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?

The description opens with a specific verb+resource, 'Get a Townhall author profile,' which clearly separates it from sibling content tools like townhall_article, townhall_headlines, and townhall_news. It does not explicitly name a sibling to contrast against, but the resource is unambiguous.

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 key selection constraint that 'exactly one is required' between slug and url, which guides invocation. However, it gives no guidance on when to prefer this over townhall_article or other author/profile siblings, so usage context 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