Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

aliexpress_category_ids

Discover AliExpress web category IDs from a keyword or category listing page; each result includes parent, depth, and full path for category inspection.

Instructions

Discover AliExpress web category ids. Returns the AliExpress web category ids that its own product cards carry on one listing page, with each id's parent, depth and full category path. Pass q to discover the categories of products matching a keyword, or category_id to inspect one category listing. Pass exactly one of them. The ids are the same web category ids used in /category//.html URLs and by the search endpoint's cat_id parameter; they are NOT the platform/taxonomy ids returned by the categories endpoint. A parent category listing contains products from its descendants, so inspecting a category reveals its child ids, and every returned path names that id's ancestors: the value space is discoverable by walking from a keyword or a category id rather than guessing.

Input Schema

NameRequiredDescriptionDefault
qNoFree-text keywords whose result cards' web category ids are returned; pass exactly one of q or category_id
pageNo1-indexed listing page to inspect (1-60), defaults to 1
category_idNoAliExpress web category id whose listing is inspected; a parent category reveals its descendants' ids. Pass exactly one of q or category_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden well: it explains the return contents (parent, depth, path), the id namespace and where those ids appear (category URLs and the search endpoint's cat_id), and the parent/descendant containment semantics. It does not cover error behavior, result-set size, or rate limits, which keeps it short of 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense but front-loaded: the return shape comes first, then the parameter routing, then the id-namespace disambiguation. Every sentence carries information, though the id-namespace and traversal explanation could be tightened into one sentence each.

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?

There is no output schema, yet the description fully specifies what comes back and how ids relate, and it resolves the one trap this tool has (confusing web category ids with taxonomy ids). An agent can call it correctly with no other information.

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 the baseline is 3, but the description adds real meaning: it explains what each mode yields (categories of matching products vs. the children of a given category) and the exclusivity constraint. Page-range semantics are left to the schema, which already documents them.

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 names a specific verb and resource ('Discover AliExpress web category ids') and states precisely what is returned: the web category ids carried on product cards, with parent, depth and full path. It explicitly distinguishes itself from the sibling categories endpoint by noting those return platform/taxonomy ids, not web category ids.

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

Usage Guidelines5/5

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

It states the two mutually exclusive modes ('Pass q to discover the categories of products matching a keyword, or category_id to inspect one category listing. Pass exactly one of them'), and names the alternative endpoint and the id family it does NOT serve. The traversal hint ('the value space is discoverable by walking from a keyword or a category id rather than guessing') tells the agent how to bootstrap without prior knowledge.

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