Crawlora MCP

tokopedia_search

Read-only

Search Tokopedia's public catalog and return paginated product-card rows with selectable filters. Use tokopedia_autocomplete for partial queries, tokopedia_search_filters for live options, or tokopedia_category for category browsing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "Query": "<Query>"
    },
    "name": "tokopedia_search"
  }
}

Input Schema

Name	Required	Description
`Page`	No	Search page from 1 through 5
`Sort`	No	Sort: 3 lowest price, 4 highest price, 5 most reviewed, 9 newest, 23 most relevant. Documented values: 3, 4, 5, 9, 23.
`Query`	Yes	Product keyword
`Filter`	No	Repeat live key:value filter selections from /tokopedia/search/filters

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.

Changed4 schema fields changedOct 7, 2026

addedInput schema / properties / Filter / description

Added value: +"Repeat live key:value filter selections from /tokopedia/search/filters"

addedInput schema / properties / Page / description
```
Added value: +"Search page from 1 through 5"
```
addedInput schema / properties / Query / description
```
Added value: +"Product keyword"
```

addedInput schema / properties / Sort / description

Added value: +"Sort: 3 lowest price, 4 highest price, 5 most reviewed, 9 newest, 23 most relevant. Documented values: 3, 4, 5, 9, 23."

First observedOct 5, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds that results are paginated product-card rows and scoped to the public catalog, which is useful context, but it does not detail rate limits, page-range limits, or result counts beyond what the schema implies. With annotations carrying the safety burden, a 3 is appropriate.

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 tight sentences with zero filler; the core search purpose and return shape are front-loaded before the routing hints. Every clause earns its place.

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?

An output schema exists so return values need not be re-explained, and annotations cover the safety profile. The description is nearly complete for an agent to call it correctly, though it could note the page-range cap (1-5) or sort semantics to fully round out the picture.

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 coverage is 100%, so the schema already documents Page, Sort, Query, and Filter. The description's mentions of 'paginated' and 'selectable filters' loosely map to Page and Filter but add no syntax or format detail beyond the schema. Baseline 3 applies 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Search) and resource (Tokopedia's public catalog) plus the return shape (paginated product-card rows with selectable filters). It explicitly names tokopedia_autocomplete, tokopedia_search_filters, and tokopedia_category as distinct siblings, so an agent can differentiate without opening schemas.

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?

Explicitly routes the agent: partial queries to tokopedia_autocomplete, live filter options to tokopedia_search_filters, category browsing to tokopedia_category. The implicit selection condition for this tool (full-keyword queries) is clear from the contrast, leaving little to inference.

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?