Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

people_headlines

Retrieve current headlines from any PEOPLE section by passing a section slug such as 'celebrity' or 'royals'.

Instructions

Get PEOPLE section headlines. Returns fresh headlines from one PEOPLE section listing page. section accepts any slug returned by GET /people/sections (37 values, too many to enumerate inline -- see that endpoint for the full, current list), for example "celebrity" or "royals".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionYesPEOPLE section slug, from GET /people/sections

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries the burden of disclosing behavior, but it only mentions 'fresh' and 'from one listing page'. It does not clarify read-only semantics, pagination, rate limits, or output structure. This is minimal coverage for a tool with zero annotation support.

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?

The description is concise at two sentences, with the purpose front-loaded and the parameter guidance compact. No superfluous content; every sentence contributes to understanding the tool.

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 single-parameter read tool with no output schema, the description covers the essential input and states the return type as headlines. However, it leaves the output format and pagination unspecified, which could be important for agents expecting a specific structure.

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 description adds significant meaning beyond the schema: it explains that section is a slug from a specific endpoint, notes that there are 37 values, and gives examples like 'celebrity' and 'royals'. This helps the agent select a valid parameter value more confidently.

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 clearly states the action (get) and resource (PEOPLE section headlines), and specifies that it returns fresh headlines from a single section listing page. It effectively distinguishes itself from article and author tools, though it does not explicitly name sibling alternatives.

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?

It instructs the agent to obtain valid section slugs from GET /people/sections and provides examples, which is useful for parameter selection. However, it does not explicitly state when to use this tool over sibling headline tools like nyt_headlines or people_news, leaving the choice to inference.

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