Crawlora MCP

zdnet_headlines

Read-only

Current ZDNet headlines for one public section; section must come from zdnet_sections.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "section": "<section>"
    },
    "name": "zdnet_headlines"
  }
}

Input Schema

Name	Required	Description	Default
`section`	Yes	ZDNet topic or content-type slug. Documented values: 5g, amazon, android, apple, ar-vr, artificial-intelligence, broadband, business, cloud, cloud-storage, collaboration, companies, computers-tech, computing, creativity-software, cyber-threats, data-centers, data-management, deals, digital-transformation, e-commerce, education, energy, enterprise-software, events, finance, fitness-bands, gaming, gaming-accessories, gaming-devices, google, hardware, headphones, health, home-and-office, home-entertainment, home-networking, home-security, how-to, innovation, ios, ipad, iphone, kitchen-household, laptops, linux, mac-os, magsafe-accessories, microsoft, mobile-accessories, mobile-carriers, mobile-os, networking, news, office-hardware-appliances, open-source, operating-systems, password-manager, pcs, photo-video, power-banks-and-batteries, productivity, projectors, quantum-computing, robot-vacuums, samsung, security, servers, services-software, sleep, smart-assistants, smart-glasses, smart-home, smart-rings, smart-watches, smartphones, social-media, space, speakers, storage, streaming-devices, streaming-services, tablets, taxes, tech, tools, transportation, tvs, video-conferencing, video-streaming-services, vpn, wearables, web-hosting, windows, windows-11, work-life, yard-outdoors.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026

addedInput schema / properties / section / description

Added value: +"ZDNet topic or content-type slug. Documented values: 5g, amazon, android, apple, ar-vr, artificial-intelligence, broadband, business, cloud, cloud-storage, collaboration, companies, computers-tech, computing, creativity-software, cyber-threats, data-centers, data-management, deals, digital-transformation, e-commerce, education, energy, enterprise-software, events, finance, fitness-bands, gaming, gaming-accessories, gaming-devices, google, hardware, headphones, health, home-and-office, home-entertainment, home-networking, home-security, how-to, innovation, ios, ipad, iphone, kitchen-household, laptops, linux, mac-os, magsafe-accessories, microsoft, mobile-accessories, mobile-carriers, mobile-os, networking, news, office-hardware-appliances, open-source, operating-systems, password-manager, pcs, photo-video, power-banks-and-batteries, productivity, projectors, quantum-computing, robot-vacuums, samsung, security, servers, services-software, sleep, smart-assistants, smart-glasses, smart-home, smart-rings, smart-watches, smartphones, social-media, space, speakers, storage, streaming-devices, streaming-services, tablets, taxes, tech, tools, transportation, tvs, video-conferencing, video-streaming-services, vpn, wearables, web-hosting, windows, windows-11, work-life, yard-outdoors."

First observedOct 7, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=true, so safety and external-fetch behavior are covered. The description adds 'current' (freshness/recency) and 'public section' (only public sections are valid), which is moderate added context but says nothing about return volume, pagination, or ordering.

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?

A single front-loaded sentence with zero filler; the scope ('one public section') and the constraint ('must come from zdnet_sections') both earn their 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?

With an output schema present, return values need no explanation, and annotations cover the safety profile. Purpose, scope, and the slug-source prerequisite are all stated, leaving only minor gaps (e.g., headline count/ordering) that an agent could tolerate.

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 enumerates the accepted slug values, so the schema does the heavy lifting. The description contributes the meaningful constraint that values must originate from zdnet_sections, but adds no syntax or semantics beyond that.

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 ('Current ZDNet headlines') plus explicit scope ('for one public section'). This clearly distinguishes it from siblings like zdnet_news (unsectioned news) and zdnet_sections (the slug source), so an agent can route without opening schemas.

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?

Explicitly requires that 'section must come from zdnet_sections,' which is an actionable prerequisite and names the sibling that supplies valid values. It does not explicitly state when to prefer this over zdnet_news or zdnet_article, so it stops short of full when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.