Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

apnews_headlines

Retrieve AP News section headlines by section slug, returning structured public editorial headlines for categories like top news, politics, business, technology, sports, and entertainment.

Instructions

Get AP News section headlines. Returns AP News headlines from a public editorial hub. The service does not bypass authentication or access controls. Billing is 1 credit, or 5 credits when browser rendering is required.

Input Schema

NameRequiredDescriptionDefault
sectionYesAP News section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations the description carries the full load, and it does add useful operational context: it is a public editorial hub, it does not bypass authentication or access controls, and it discloses billing tiers (1 credit, or 5 with browser rendering). However, it says nothing about what the response contains, pagination, or rate limits, leaving real gaps for a data-retrieval tool.

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 purpose. The second sentence ('Returns AP News headlines from a public editorial hub') mildly restates the first, but the billing and auth sentences each add new information, so waste is limited.

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

Completeness3/5

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

For a simple one-parameter reader with no output schema and no annotations, the description covers purpose, legal posture, and cost, but omits return shape and volume. It is minimally adequate rather than complete.

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 of valid section slugs is fully enumerated, so the schema already documents the sole parameter. The description adds no format or semantics beyond it, making the baseline 3 appropriate.

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?

Clear verb+resource: 'Get AP News section headlines' states exactly what the tool returns. It does not name siblings like apnews_news or apnews_sections, so an agent must infer the boundary between a headlines list and a full news feed. Still, the resource and scope are unambiguous.

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 – the agent can infer it should pass a section slug to fetch that section's headlines, but there is no explicit when-to-use versus apnews_news/sections or any exclusion. No prerequisites or alternatives are stated.

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