Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

apnews_sections

List the 11 AP News section hubs, including top news, politics, business, and sports, to select valid section slugs for headlines queries.

Instructions

Get AP News sections. Lists the 11 AP News hubs accepted by apnews-headlines: ap-top-news, us-news, world-news, politics, business, technology, science, health, sports, entertainment and lifestyle. Each has a slug, display name and hub url. The Fact Check page is served by apnews-fact-check instead.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden, and it does disclose the return shape (each entry has a slug, display name, and hub url) plus the fact that the Fact Check section is served by a different tool. It omits any statement of read-only nature or staleness, but for a static parameterless catalog this is largely self-evident.

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?

Two tight sentences: the purpose is front-loaded, then the value list adds genuine information. The closing note about the Fact Check page earns its place by preventing a misrouting to this tool.

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?

With no output schema and no parameters, the description fully covers what an agent needs: what it returns, the exact hub slugs, their field shape, and where the Fact Check page lives instead. Nothing material is missing for such a simple lookup.

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?

Zero parameters, so the baseline is 4. The description goes further by listing the actual accepted values, which compensates for the missing output schema, though these are return values rather than parameter semantics.

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?

Specific verb ('Get') plus resource ('AP News sections'), and it enumerates all 11 hub slugs, which distinguishes it from sibling tools like apnews_headlines and apnews_news at a glance. An agent knows exactly what this returns without opening a schema.

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?

It clearly ties itself to the consumer tool ('the 11 AP News hubs accepted by apnews-headlines') and routes the Fact Check page to apnews-fact-check, which is strong context. It stops short of an explicit 'use this before calling apnews_headlines to discover valid slugs' instruction, but the relationship is unambiguous.

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