Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cnet_article

Extract public article metadata and body paragraphs from a canonical CNET URL, returning clean JSON and reporting video-only or bodyless pages as errors.

Instructions

Get CNET article content. Returns public CNET article metadata and body paragraphs from a canonical article URL. CNET articles are freely readable; video-only pages and pages without an article body are reported as upstream errors rather than returned empty.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical CNET article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that CNET articles are freely readable and that video-only/no-body pages are reported as errors. It does not explicitly confirm a read-only operation or mention other behaviors like rate limits, but the provided failure modes are useful.

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 sentences, no filler, with the primary purpose front-loaded and error behavior clearly stated in the second sentence. Every word earns its place.

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 straightforward single-URL fetch tool, the description explains what is returned (metadata and body paragraphs), that content is public, and how edge cases (video-only/no-body) are handled. It is slightly light on exact return structure, but that is less critical given the simple parameter set.

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?

The schema already has 100% coverage for the single parameter, describing it as 'Canonical CNET article URL.' The description repeats the same qualifier and adds no beyond-schema parameter meaning, so the baseline of 3 applies.

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?

The description states a specific verb and resource ('Get CNET article content') and specifies the return payload (metadata and body paragraphs) from a canonical URL. This clearly distinguishes it from sibling CNET tools like cnet_headlines, cnet_news, or cnet_sections.

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 usage by requiring a canonical article URL and notes that video-only or body-less pages produce upstream errors. However, it does not name alternative sibling tools or provide explicit when-not conditions beyond these error cases.

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