Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

xda_article

Fetch structured XDA article content from a canonical www.xda-developers.com// URL, returning title, authors, section, lead image, body paragraphs, and paywall status.

Instructions

Get XDA article content. Returns one XDA article by its url, which must be a www.xda-developers.com/<slug>/ link; section hubs, author pages and the bare xda-developers.com host are rejected. The response has the title, description, times, section, authors, lead image and body paragraphs. paywalled is set to true only if the page declares the article not free.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical XDA article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it enumerates the returned fields (title, description, times, section, authors, lead image, body paragraphs) and discloses the non-obvious paywall flag behavior. It omits auth requirements, rate limits, or caching/live-fetch behavior, so it falls short of maximal transparency.

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, tightly front-loaded: purpose first, then the URL constraint, then the response shape and the paywall edge case. No filler and nothing redundant.

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-param tool with no output schema and no annotations, the description covers the input constraint, return fields, and the paywall edge case well. Minor gaps remain (what 'times' means, no output schema backing), but an agent has what it needs to call it correctly.

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 schema already calls the param a 'Canonical XDA article URL', but the description adds real value by specifying the required host/slug shape and the URL classes that will be rejected. That goes beyond the schema's generic phrasing.

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 article content... Returns one XDA article by its url') and carves out the boundary against siblings by specifying that section hubs and author pages are rejected, which maps onto xda_sections and xda_author. An agent can tell exactly which tool to call without opening the schema.

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?

Gives explicit positive and negative conditions: the url must be a www.xda-developers.com/<slug>/ link, while section hubs, author pages and the bare host are rejected. It does not name the alternative tools to use for those rejected cases, so routing is implied rather than stated.

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