Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cbsnews_headlines

Fetch headlines for a chosen CBS News section by passing its slug, such as politics or technology. Get titles, URLs, and optional summaries, authors, dates, and images.

Instructions

Get CBS News section headlines. Returns fresh headlines for one CBS News section. section is required and is one of main, us, world, politics, moneywatch, health, entertainment, science, technology or space. Each item has a title and URL, and may also carry a summary, author, publication time and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesCBS News RSS section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the return-item shape (title, URL, and optional summary/author/time/image), which is useful, but says nothing about freshness guarantees, rate limits, or fetch behavior beyond the word 'fresh'.

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?

Three tight sentences, front-loaded with the primary action and scope, then the parameter, then the return shape. Listing all ten enum values is slightly redundant against the schema but does not impair readability.

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 usefully documents the item fields the caller will receive. For a single-parameter read-only feed tool this is nearly complete; only freshness/collection semantics are unspecified.

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 description coverage is 100% and the enum is fully specified in the schema, so the baseline is 3. The description restates the valid sections and reiterates that `section` is required, which duplicates rather than extends 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?

States a specific verb (Get) and resource (CBS News section headlines) with clear scope ('one CBS News section'). It does not explicitly differentiate itself from close siblings like cbsnews_news, cbsnews_sections, or cbsnews_article, so it stops short of a 5.

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?

Usage is implied by the required `section` parameter and the enumeration of valid values, but the description never states when to prefer this tool over cbsnews_news or cbsnews_article, nor any exclusions. It is adequate but leaves routing 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