Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

townhall_article

Retrieve Townhall article content from a canonical URL, returning metadata and body paragraphs. VIP stories are flagged as paywalled, providing only free lead paragraphs.

Instructions

Get Townhall article content. Returns public Townhall article metadata and body paragraphs from a canonical news or column URL. VIP stories are flagged with paywalled and return only the free lead paragraphs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical Townhall article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral disclosure burden. It does well by noting that only public content is returned and that VIP stories are 'flagged with paywalled' and return only free lead paragraphs. This is a meaningful limitation beyond the basic fetch behavior.

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?

The description is two sentences, front-loaded with the core purpose, and every sentence contributes necessary information: what is returned, the required URL type, and the VIP/paywall behavior. There is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter article-fetch tool with no output schema, this description is complete. It specifies the input, the return contents, and the paywall limitation, giving an agent enough context to invoke the tool and understand what to expect.

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 coverage is 100%, and both the schema and description describe the URL as canonical. The description adds a slight clarification that it should be a 'news or column URL,' but it does not substantially enrich the parameter meaning beyond what the schema already provides.

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 names a specific verb, resource, and output: 'Get Townhall article content' returning 'metadata and body paragraphs.' It clearly distinguishes this article-content tool from sibling tools like townhall_author, townhall_headlines, and townhall_sections.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description conveys the appropriate context: use this tool when you have a 'canonical news or column URL' and need article content. It does not explicitly name alternatives or exclusions, but the context is clear enough for an agent to choose this over headline or section tools.

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