Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

zdnet_headlines

Fetch ZDNet headlines for a chosen section to track news on topics like AI, security, or smartphones. Provide a valid section slug to get a clean list without video pages.

Instructions

Get ZDNet section headlines. Lists fresh ZDNet headlines for one topic or content type. section is required and takes a slug such as artificial-intelligence, security, smartphones, vpn, how-to or news; zdnet-sections lists all of them. Video pages are dropped, and an invalid value returns a 400 error.

Input Schema

NameRequiredDescriptionDefault
sectionYesZDNet topic or content-type slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.2/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 behavioral burden; it does disclose that video pages are dropped and invalid values return a 400 error. It does not describe result count, ordering, pagination, authentication, or output shape, leaving meaningful gaps for a no-annotation tool.

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?

The description is three tight sentences, front-loading the purpose before the required parameter and edge behavior. There is no filler; each clause adds scope, parameter guidance, or error behavior.

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 simple one-parameter listing tool with a rich enum schema and no output schema, the description covers purpose, required input, valid examples, sibling routing, and error behavior. It still omits return format and pagination details, so it is strong but not fully complete.

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 enum is fully documented in the schema, so baseline is 3. The description earns additional credit by giving representative slug examples, reiterating requiredness, and pointing to `zdnet-sections` for the full list.

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 opens with a specific verb and resource ('Get ZDNet section headlines') and defines scope as one topic or content type. It explicitly names `zdnet-sections` as the way to list all sections, so an agent can distinguish this headline fetcher from the section-listing sibling.

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?

It explains that `section` is required, gives example slugs, and points to `zdnet-sections` for enumerating valid sections. However, it does not explicitly state when to use this tool versus `zdnet_news` or `zdnet_article`, so the guidance is clear but not fully exclusionary.

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