Crawlora MCP

aliexpress_category_ids

Read-only

Discover AliExpress WEB category ids from the category breadcrumbs its own product cards carry: pass q (free-text keywords) to discover the web categories of matching products, or category_id (a web category id from a /category//.html URL) to inspect one category listing -- pass exactly one. Each result carries category_id, parent_id, level, leaf, product_hits and the full observed path. These are the ids aliexpress_category_products and aliexpress_search's cat_id accept; they are NOT the platform/taxonomy ids aliexpress_categories returns. A parent category listing contains products from its descendants, so inspecting a category reveals child ids, and each path names an id's ancestors: walk the tree from a keyword or any category id instead of guessing ids. page is 1-indexed (1-60) and defaults to 1.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "aliexpress_category_ids"
  }
}

Input Schema

Name	Required	Description
`q`	No	Optional. Free-text search keywords whose result cards' web category ids are returned, e.g. 'wireless earbuds'. Pass exactly one of q or category_id.
`page`	No	Optional. 1-indexed listing page to inspect, defaults to 1. Each page carries up to 60 products and therefore several category paths.
`category_id`	No	Optional. AliExpress web category id (the number in a /category/<id>/<slug>.html URL) whose listing is inspected. A parent category lists products from its descendants, so its cards reveal child ids. Pass exactly one of q or category_id.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover read-only and open-world. The description adds genuinely useful behavior: each result carries category_id, parent_id, level, leaf, product_hits and full observed path, and parent listings surface descendant products, which explains why a listing can reveal child ids. It does not mention rate limits or page-boundary edge behavior beyond the 1-60 range, so it stops short of full transparency.

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 well ordered: capability first, parameters second, id-family disambiguation third, tree-walking guidance fourth. It is one long compound opening sentence that is slightly run-on, but almost every clause carries actionable information.

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?

For a discovery/navigation tool with an output schema and three optional params, the description covers what it returns conceptually, how parents/children relate, and how to iterate the tree. Nothing an agent needs in order to call it correctly is missing.

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; the description still adds interpretation, notably that page ranges 1-60 and each page holds up to 60 products and therefore several category paths, and that category_id is the number in a /category/<id>/<slug>.html URL. Most of the q/category_id exclusivity restates the schema, so it is an add-on rather than a necessity.

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 — discover AliExpress WEB category ids from category breadcrumbs on product cards — and explicitly contrasts them with the platform/taxonomy ids that aliexpress_categories returns. An agent can distinguish this from every sibling in the aliexpress_* family 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 Guidelines5/5

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

Gives the mutually exclusive selection rule ('pass exactly one' of q or category_id) and prescribes a workflow: 'walk the tree from a keyword or any category id instead of guessing ids.' It also names the downstream consumers of the returned ids (aliexpress_category_products, aliexpress_search's cat_id), so the agent knows when this tool is the prerequisite step.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?