Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

xda_author

Fetch an XDA author profile from a canonical author URL to get name, title, bio, image, social links, and latest articles.

Instructions

Get an XDA author profile. Returns an XDA author profile from their https://www.xda-developers.com/author/<slug>/ url (required; paginated author URLs are rejected). The response has the name, title, biography, image, social links and the profile's latest articles, about 20, with no older pages.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical XDA author 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?

With no annotations, the description carries the full burden and does well: it enumerates the returned fields (name, title, biography, image, social links, latest articles) and discloses a real behavioral limit ('about 20, with no older pages'). It omits auth needs and rate limits, which keeps it from a 5.

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?

Two sentences, fully front-loaded with the purpose first, then the input contract and return shape. Every clause adds information; no filler.

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 the response, and it does, including the ~20-article cap and absence of older pages. Combined with complete param coverage, an agent has everything needed 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%, so baseline is 3, but the description adds genuine meaning beyond the schema's bare 'Canonical XDA author URL': it supplies the URL template and the constraint that paginated author URLs are rejected.

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 an XDA author profile') and pins it to the XDA author-URL namespace, so it is clearly distinct from siblings like xda_article, xda_news, and xda_headlines.

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 clear context for invocation ('url' required, canonical author URL) plus an explicit exclusion ('paginated author URLs are rejected'). It does not, however, route the agent to an alternative tool for paginated cases, so it stops short of full when/when-not/alternatives guidance.

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