Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cnet_headlines

Retrieve CNET headlines for a chosen topic section by providing a required slug such as ai or deals. Returns each article’s title and URL, plus summary, author, time, or image when available.

Instructions

Get CNET section headlines. Returns fresh CNET headlines for one topic. section is required and takes a topic slug such as ai, deals, smart-home, electric-vehicles or tv-and-movies; an invalid value returns a 400 error. Each item has a title and URL, and may also carry a summary, author, publication time and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesCNET topic slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.2/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 does so reasonably: it discloses error behavior (invalid value returns 400) and the return shape (title + URL required, summary/author/time/image optional). It stops short of documenting auth needs, rate limits or ordering/freshness semantics.

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?

Four sentences, front-loaded with purpose then parameter behavior then return shape; each carries useful information. Slightly more than strictly necessary but no filler.

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?

With a single required parameter, no output schema and no annotations, the description covers purpose, parameter format, error behavior and the returned fields, which is everything an agent needs to call 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?

Schema coverage is 100% with a 51-value enum, so the baseline is 3, but the description adds value beyond the schema by naming representative slugs and specifying the failure mode (400) for invalid values. It doesn't describe slug discoverability or casing rules.

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 CNET section headlines") scoped to a single topic, which distinguishes it from cnet_news, cnet_sections and cnet_article. An agent can tell it fetches curated headlines per section without opening the schema.

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 makes clear the tool is for a single topic per call and that `section` is required, but it never names an alternative (e.g. cnet_news for broader coverage) or states when not to use it. Usage is implied rather than explicit.

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