Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

androidauthority_headlines

Fetch Android Authority section headlines by slug to get the newest 10-20 stories with titles, URLs, authors, images, and optional summaries or dates.

Instructions

Get Android Authority section headlines. Returns the newest 10 to 20 stories from one Android Authority section hub. section is required and takes a slug such as reviews, how-to, smartwatches or android-phones. Each item has a title, URL, author and image; summary appears on the lead story of a hub, and published_at only on stories more than a day old.

Input Schema

NameRequiredDescriptionDefault
sectionYesAndroid Authority section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/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 discloses the return size (10-20 stories), the per-item fields (title, URL, author, image), and the conditional fields (summary only on the lead story, published_at only on stories over a day old). It omits any auth or rate-limit context, but for a read-only feed that is a minor gap.

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?

Three sentences, front-loaded with purpose, then scope, then return shape. Every sentence carries information and nothing is wasted, though the field-by-field sentence is dense.

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 no output schema, the description steps in to describe the returned item fields and their conditional presence, which is exactly what an agent needs. Combined with the enum-backed required parameter, the definition is nearly complete for a single-parameter feed tool.

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 coverage is 100% and the enum already enumerates all valid slugs, so the schema does the heavy lifting. The description's example slugs (reviews, how-to, smartwatches, android-phones) add only marginal value over the existing enum. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Get Android Authority section headlines') and scopes it precisely to one section hub returning the newest 10-20 stories. It is clearer than most siblings, though it does not explicitly contrast itself with androidauthority_news or androidauthority_article.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description notes that `section` is required and gives example slugs, which implies usage, but it never states when to choose this tool over androidauthority_news, androidauthority_sections, or androidauthority_article. No when-not guidance is provided.

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