Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

townhall_headlines

Fetch headlines from a chosen Townhall section (news, columnists, or topics like congress, economy, iran). Returns up to 30 stories with title, URL, image, and optional author, time, and summary.

Instructions

Get Townhall section headlines. Lists headlines for one Townhall section. section is required: news and columnists return the 20 most recent stories, while the topic sections (such as congress, economy or iran) return up to 30 stories mixing news and columns. Items carry title, URL, image and, when available, author, time and summary.

Input Schema

NameRequiredDescriptionDefault
sectionYesTownhall section slug

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 full burden, and it does disclose real behavior: news/columnists return 20 most recent stories while topic sections return up to 30 mixed news/columns, and items carry title, URL, image and optional author/time/summary. It stops short of stating read-only nature, pagination, or auth requirements.

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 front-loaded sentences that move from purpose to parameter semantics to return payload, with no filler. The most decision-relevant fact, that section is required and governs result size, comes early.

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 exists, so the description usefully compensates by enumerating the returned item fields (title, URL, image, optional author/time/summary) and the per-section result counts. Missing only read-only confirmation and pagination behavior, which keeps it just under fully complete.

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 enum is fully documented as 'Townhall section slug', so the schema sets the baseline. The description adds genuine value beyond it by grouping the slugs semantically (news/columnists vs topic sections) and tying each group to a distinct result volume and content mix.

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 and resource ('Get Townhall section headlines', 'Lists headlines for one Townhall section'), so an agent immediately knows this is a section-scoped headline lister. It does not name sibling tools (townhall_news, townhall_sections, townhall_article), so it stops short of full sibling differentiation.

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 rather than instructed: the description explains that section determines result set and count, but never says when to pick this over townhall_news, townhall_sections or townhall_article, nor any prerequisites. Adequate context, no explicit alternatives or exclusions.

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