Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

thehill_headlines

Retrieve current headlines for one The Hill section by slug, returning each item's title, URL, summary, author, and publication time.

Instructions

Get The Hill section headlines. Returns the current headlines for one The Hill section. section is required and takes one of 19 slugs, including home, policy, business, senate, national-security and technology. Each item has its title and URL, plus summary, author, publication time and image when the outlet provides them, and the response echoes the section.

Input Schema

NameRequiredDescriptionDefault
sectionYesThe Hill RSS section slug

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 burden and does disclose the return shape: title, URL, plus summary, author, publication time and image 'when the outlet provides them', and that the response echoes the section. It could say more about it being a read-only fetch (implied) but the return-field detail is genuinely useful.

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 core purpose and efficiently covers parameter and return details. Slight redundancy between the first two sentences ('section headlines' / 'headlines for one section') but otherwise tight.

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 single-parameter read tool with no output schema, the description covers purpose, the required parameter, and the return fields comprehensively. Nothing an agent needs to call it correctly is missing.

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% — the enum already enumerates all values and the schema describes section as 'The Hill RSS section slug'. The description adds the count (19) and a few illustrative slugs, but this largely repeats structured data, so the baseline 3 applies.

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+resource: 'Get The Hill section headlines' and clarifies it returns current headlines for a single section. Clear purpose, though it does not explicitly differentiate from the nearby sibling thehill_news or thehill_sections.

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: pick one section and fetch its headlines, with examples of valid slugs given. However, there is no explicit when-to-use guidance versus alternatives like thehill_news or thehill_sections, and no note that thehill_sections can enumerate the valid slugs.

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