Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cnn_live_story

Fetch a CNN live story from its canonical cnn.com live-news URL and return the title, description, last update time, and chronological posts with text and timestamps.

Instructions

CNN live story updates. Returns a CNN live story from its canonical cnn.com live-news url: title, description, last update time and the posts in chronological order. Each post has an id, title, paragraphs of text, and published and updated times.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical cnn.com live-news URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the return shape (title, description, last update time, chronological posts, and each post's id/title/paragraphs/timestamps). It does not cover auth, error behavior, or rate limits, but the read-only nature is clear from 'Returns'.

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?

Front-loads the purpose in the first clause, then details the output structure in a compact two-sentence block. Dense but every clause earns its place with no filler.

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?

With no output schema, the description must (and does) explain return values, making it reasonably complete for a single-parameter read tool. The main missing piece is routing guidance versus sibling article tools, which is a usage gap rather than a completeness one.

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?

Only one parameter with 100% schema coverage, so the schema already documents 'url' as a canonical cnn.com live-news URL. The description restates the same constraint without adding format examples or validation detail. Baseline 3 is 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?

States a specific verb ('Returns') and resource ('CNN live story') scoped to live-news content, and enumerates the fields returned. It distinguishes itself from a generic article tool by emphasizing 'live story' and 'live-news url', but never explicitly names the sibling cnn_article to disambiguate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies a canonical cnn.com live-news URL is required, but gives no when-to-use guidance, no exclusions, and no mention of the alternative cnn_article tool for non-live coverage. The agent must infer selection from the name alone.

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