Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cnbc_headlines

Retrieve current CNBC headlines for any editorial section. Supply a section slug to get titles, article URLs, and card metadata as structured JSON.

Instructions

CNBC section headlines. Returns current server-rendered CNBC headlines for one public editorial section, including title, article URL, and card metadata when available. Use /cnbc/categories to discover the supported section slugs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionYesPublic CNBC editorial section slug from /cnbc/categories

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and provides useful context: results are current and server-rendered, limited to one public section, and metadata is included only when available. It does not mention pagination, rate limits, or error behavior, but for a simple read-only headlines tool it gives meaningful transparency.

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 concise sentences with no filler. The core purpose and return contents are front-loaded, and the prerequisite discovery step is stated efficiently.

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

Completeness4/5

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

For a single-parameter headlines tool with no output schema, the description adequately explains what is returned and how to obtain a valid section slug. It does not specify result count or ordering, but the tool is simple enough that the description is largely 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 schema already describes the section parameter as a public CNBC editorial section slug. The description reinforces that /cnbc/categories is the source of valid slugs, adding a small amount of practical guidance beyond the schema.

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 a specific action and resource: returning current CNBC headlines for one public editorial section, including title, article URL, and card metadata. It does not explicitly contrast itself with sibling tools like cnbc_article or other headline tools, so it stops short of full sibling differentiation.

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?

The description implies when to use the tool by specifying it returns section headlines and directs the agent to /cnbc/categories for valid slugs. It does not explicitly state when to prefer this over alternatives or when not to use it, leaving usage guidance mostly implicit.

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