Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

theatlantic_headlines

Retrieve current article cards from any The Atlantic section, including title, URL, description, byline, and publication time. Get structured JSON for specific sections like politics or science.

Instructions

Get the latest stories in an Atlantic section. Returns the current front-page article cards for one Atlantic section: each story's title, canonical URL, description, byline, publication time, and lead image. Section must be a slug returned by /theatlantic/sections.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionYesSection slug from /theatlantic/sections

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?

No annotations are present, so the description carries the burden. It discloses that the tool returns current front-page article cards and enumerates the exact fields (title, URL, description, byline, publication time, lead image), which is useful behavioral context. It doesn't mention pagination, ordering, or rate limits, but for a simple read-only headlines tool this is sufficient.

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 sentences with no filler; the main action is front-loaded, output fields are compactly listed, and the input constraint is stated last. Every sentence earns its place.

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 one-parameter tool with a full enum, the description provides enough context to invoke it correctly: what it returns, the field list, and where to get a valid slug. Since there is no output schema, the description's return-field enumeration is especially valuable.

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 the enum already documents all valid section slugs. The description reinforces that the slug must come from /theatlantic/sections, but doesn't add meaning beyond the schema's parameter description.

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?

States a specific verb ('Get'), resource ('latest stories in an Atlantic section'), and output scope (front-page article cards with listed fields). It clearly differentiates from sibling tools like theatlantic_article and theatlantic_sections by focusing on section-level headlines.

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?

Gives a clear prerequisite: section must be a slug returned by /theatlantic/sections, which routes the agent to the correct companion tool. It doesn't explicitly contrast with alternatives such as theatlantic_article for full story content, so no exclusion guidance is provided.

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