Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

propublica_headlines

Fetch ProPublica headlines for one topic slug, returning recent stories with title, URL, publication time, and author.

Instructions

Get ProPublica topic headlines. Returns the latest ProPublica stories for one topic. section is required and takes one of 33 topic slugs, such as politics, health-care, immigration, courts, environment or trump-administration. Each item has its title, URL, publication time and author.

Input Schema

NameRequiredDescriptionDefault
sectionYesProPublica topic slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It does disclose the shape of returned items (title, URL, publication time, author), which is genuine behavioral context, but says nothing about permissions, rate limits, pagination, or freshness guarantees.

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?

Three short sentences, front-loaded with the core action, followed by the required-parameter constraint and the return shape. Nothing is redundant, though the middle sentence partly restates the first.

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?

For a one-parameter, read-only lookup with no output schema, the description supplies the needed context: required enum input plus the fields each item contains. Only pagination/limit behavior is left unaddressed.

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 description coverage is 100% and the enum already enumerates all 33 valid slugs, so the schema does the heavy lifting. The description's example slugs (`politics`, `health-care`, `immigration`, etc.) add a little orientation but no syntax or format detail beyond the schema.

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 ProPublica topic headlines") and clarifies scope: latest stories for exactly one topic. It is distinguishable from generic news tools, though it does not explicitly say how it differs from siblings like propublica_news or propublica_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 only implied by the required `section` slug — an agent can infer this is a browse-by-topic tool. There is no statement of when to prefer it over propublica_news, propublica_sections, or propublica_article, and no exclusions or prerequisites.

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