Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

huffpost_sections

List HuffPost topic hubs with their slugs, names, and URLs so you can choose valid sections for headline queries. Excludes games, horoscopes, newsletters, and international editions.

Instructions

Get HuffPost sections. Lists the topic hubs accepted by huffpost-headlines, such as news/politics, impact/business, life/travel and voices/latino-voices. Each entry has a slug, display name and hub url. Games, Horoscopes, Newsletters and HuffPost's international editions are excluded.

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 reasonably well: it discloses the return fields (slug, name, url) and the exclusion set (Games, Horoscopes, Newsletters, international editions). That negative scope is genuinely useful coverage information. It does not discuss ordering, pagination, or freshness, but for a small static lookup this is solid.

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?

Four short sentences, each earning its place: purpose, relationship to sibling tool, return shape, and exclusions. Purpose and the sibling link are front-loaded, and nothing is redundant.

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?

There is no output schema, yet the description names the fields each entry returns, plus examples of the slug format and the excluded categories. For a parameterless read tool this is everything an agent needs to call and consume it correctly.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate.

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 and resource ('Get HuffPost sections') and immediately situates itself against a named sibling, huffpost_headlines, which consumes these values. An agent can distinguish it from the many *_sections and *_headlines siblings 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?

Explains the operative context: these slugs are 'accepted by huffpost-headlines', which effectively tells the agent this is the lookup that feeds the headlines tool. It also states exclusions. It stops short of an explicit when-not-to-use or a contrast with huffpost_news, so it is clear but not fully prescriptive.

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