Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

xda_headlines

Fetch 10 recent XDA headlines for a required section slug, such as news, reviews, gpu, or windows. Valid slugs only; use section listings to avoid invalid or dormant sections.

Instructions

Get XDA section headlines. Lists 10 recent XDA items for one section. section is required and takes a slug such as news, reviews, buying-guides, gpu, laptops, windows, linux-hub or ai-tools; xda-sections lists them all. Dormant sections such as editorials or beats return old items. Other values are rejected.

Input Schema

NameRequiredDescriptionDefault
sectionYesXDA RSS section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden well: it discloses the fixed result size (10 items), the dormant-section edge case (returns stale items), and the rejection behavior for invalid slugs. These are useful non-obvious traits beyond the schema.

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?

The core action is front-loaded in the first sentence, and the parameter/edge-case details follow compactly. It is appropriately sized with little waste, though the example list is a bit long.

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 single required-parameter headlines tool with no output schema, it covers the action, return volume (10 items), parameter constraints, and error behavior. Little an agent needs to invoke 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% with an enum, so the baseline is 3; the description adds value by supplying representative slugs and clarifying semantics (dormant vs active sections, rejection of invalid values). It goes beyond a bare restatement of the enum.

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 XDA section headlines") and immediately narrows scope ("Lists 10 recent XDA items for one section"). It distinguishes itself from siblings like xda_news and xda_article, and explicitly routes to xda-sections for the section list.

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?

Provides clear context: section is required, gives valid example slugs, points to xda-sections for enumerating them, and warns that dormant sections return old items while other values are rejected. It stops short of explicitly contrasting when to use this vs xda_news for general headlines.

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