Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

androidpolice_author

Fetch an Android Police author's byline, biography, social links, and recent articles from a canonical profile URL. Returns first-page data only.

Instructions

Get an Android Police author profile. Returns a public author's byline metadata, biography, social links, and recent articles from a canonical author URL. Only the first page is covered because author pagination is disallowed by robots.txt.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical Android Police author URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

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 it delivers real behavioral context: the profile is public, it returns bio/social links/recent articles, and critically it discloses that only page one is available because author pagination is disallowed by robots.txt. It omits auth/rate-limit details, but the pagination constraint is a meaningful disclosure.

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 tight sentences, front-loaded with purpose followed by return contents and then the pagination caveat. Nothing is padded, though the return-value enumeration slightly overlaps the purpose sentence.

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?

No output schema exists, so the description correctly enumerates the returned fields and the pagination limitation. For a single-param read tool this is nearly complete; only error handling for malformed/non-canonical URLs is unaddressed.

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 description coverage is 100% and the single `url` param is fully documented as a canonical Android Police author URL; the description repeats that constraint without adding format, example, or validation detail. Baseline 3 is appropriate when the schema does the heavy lifting.

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 and resource ("Get an Android Police author profile") and enumerates the payload (byline metadata, biography, social links, recent articles). An agent can distinguish it from androidpolice_article/news/headlines, though it names no explicit sibling alternative.

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?

Usage is only implied: the tool takes a canonical author URL, so an agent with such a URL can infer when to call it. There is no statement of when-not-to-use it and no pointer to the alternative androidpolice_* tools for article-level retrieval.

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