Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

androidauthority_sections

List all 44 Android Authority section slugs accepted by the headlines tool, covering news, reviews, best, how-to, deals, and top-level topic hubs with names and URLs.

Instructions

Get Android Authority sections. Lists the 44 Android Authority sections that androidauthority-headlines accepts: the content-type hubs (news, reviews, best, how-to, features, deals, authority-insights), the top-level topic hubs and their sub-hubs. Each has a slug, display name and page url. Tag archives are not sections.

Input Schema

NameRequiredDescriptionDefault

No arguments

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, the description carries the full burden, and it does disclose the shape of the return (each item has `slug`, `name`, `url`), the exact cardinality of the result set (44), and a boundary condition (tag archives excluded). That covers what an agent needs to consume the output; it does not discuss caching/staleness or whether the list is paginated, which is a minor residual gap for a static enumeration.

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 the purpose, then the composition of the list, then the return fields and the exclusion. The parenthetical enumeration of seven hub slugs is slightly verbose but genuinely helps an agent recognize valid values, so it earns its space. No filler.

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?

There is no output schema, no input schema properties, and no annotations, so the description must supply everything, and it largely does: count, categories, excluded content, and returned fields. Only marginal details (exact JSON wrapper, whether sub-hubs are flattened into the same list) are left unspecified.

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 tool takes zero parameters, so the baseline is 4. The description correctly adds no parameter talk; instead it describes the keys present in each returned record, which is the relevant semantic content for a parameterless lister.

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 Android Authority sections") and then defines the resource precisely: the 44 sections accepted by `androidauthority-headlines`, split into content-type hubs and topic/sub-hubs. It also contrasts the resource against a near-neighbour that an agent might confuse it with ("Tag archives are not sections"), so it is distinguishable from sibling listings without opening a 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?

The phrase "the 44 sections that `androidauthority-headlines` accepts" gives clear context for when to call this: to discover valid section identifiers before querying headlines. The exclusion of tag archives is a useful when-not clause. It stops short of explicitly directing the agent (e.g. "call this first to obtain a valid slug for androidauthority_headlines"), so it is strong but not fully prescriptive.

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