Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

zdnet_article

Fetch one ZDNet article, review, or how-to using its canonical zdnet.com URL, returning title, dates, authors, image, and body paragraphs. Unsupported pages return an error.

Instructions

Get ZDNet article or review content. Returns one ZDNet article, review or how-to by its canonical zdnet.com url. The response has the title, description, published and updated times, section labels, authors, lead image and body paragraphs. Video, topic and author pages are not supported and return an error instead of an empty article.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical ZDNet article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations present, the description carries the burden and does well: it enumerates the returned fields and specifies that unsupported page types return an error rather than an empty article. It omits any note on auth, rate limits, or caching, so it is not fully exhaustive.

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?

Three sentences, front-loaded with the action and resource, then return shape, then the failure case. No filler and each sentence adds distinct information.

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?

There is no output schema, so the description plausibly compensates by listing the response fields (title, times, sections, authors, lead image, paragraphs) and the error behavior. For a one-parameter fetch tool, nothing needed to call it correctly is missing.

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% and the single param is documented there, so baseline is 3. The description adds real meaning by stating the URL must be canonical to zdnet.com and that only article/review/how-to URLs succeed, clarifying what a valid value looks like beyond the schema.

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 ZDNet article or review content') and narrows scope to a single article/review/how-to fetched by URL. This cleanly separates it from list-oriented siblings like zdnet_headlines, zdnet_news, and zdnet_sections.

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

Usage Guidelines4/5

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

Says to use it with a canonical zdnet.com URL and explicitly excludes video, topic, and author pages, which error out. That is clear when-not guidance, but it doesn't name an alternative tool for those excluded page types.

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