Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

androidauthority_article

Fetch a canonical Android Authority article by URL and return structured JSON with title, metadata, authors, images, paragraphs, TL;DR, and pros/cons; non-article pages are rejected.

Instructions

Get Android Authority article content. Returns an Android Authority article by url, a canonical androidauthority.com address whose path is one slug ending in the numeric post id: title, description, publication and update times, section, authors, image and body paragraphs, with TL;DR and pros/cons bullets as separate entries. Section, tag and author pages are rejected, and an unknown post id returns not-found.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical Android Authority 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?

No annotations are provided, so the description carries the full burden. It discloses the returned fields (title, description, times, section, authors, image, body paragraphs, TL;DR, pros/cons) and two error behaviors: non-article pages are rejected and unknown post IDs return not-found. It does not mention auth, rate limits, or content truncation, but for a read-only article fetch this is solid.

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 core purpose, then return shape, then error semantics. No filler; every clause adds 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?

No output schema exists, so the description must describe return values, and it does so comprehensively (title, description, publication/update times, section, authors, image, body paragraphs, TL;DR, pros/cons). It also covers error behavior, making it complete for this read-only article endpoint.

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?

The schema documents the single `url` parameter, so baseline is 3. The description adds meaningful semantics by explaining that the URL must be canonical and its path must be one slug ending in the numeric post ID, which clarifies the expected format beyond the schema's text.

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 states a specific verb ('Get') and resource ('Android Authority article content'), and differentiates from sibling endpoints by noting that section, tag, and author pages are rejected. This lets an agent distinguish it from tools like androidauthority_sections or androidauthority_headlines 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?

It specifies the required URL format (canonical androidauthority.com with one slug ending in a numeric post id) and explicitly rejects section/tag/author pages, giving clear when-to-use and when-not-to-use guidance. It does not name alternative tools, so it stops short of a 5.

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