Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tokopedia_autocomplete

Get Tokopedia search suggestions for a partial product keyword. Returns canonical product-search URLs to speed keyword research and query building.

Instructions

Autocomplete Tokopedia product searches. Returns current public Tokopedia search suggestions for a partial keyword. Suggestions include canonical product-search URLs and are not product-search results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesPartial product keyword, up to 100 characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the main burden. It does disclose useful behavior: the output is public, current, and consists of suggestions with canonical product-search URLs rather than product results. It does not mention rate limits, authentication, or side effects, though this is a low-risk read-type tool.

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?

The description is two short sentences with no filler. The first states the operation, the second adds a useful clarifying distinction, and the information is front-loaded.

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?

For a one-parameter autocomplete tool with no output schema, the description covers the essential points: what input it takes, what it returns, and that suggestions are not product results. More detail on output shape or locale context could help, but the tool is simple enough that these are not required for correct invocation.

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?

The single parameter is already fully described in the schema as a partial keyword up to 100 characters, and the description adds little beyond that. With 100% schema description coverage, the baseline of 3 is appropriate.

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 states a clear, specific action: it returns current public Tokopedia search suggestions for a partial keyword. It also explicitly differentiates itself from product-search results, so an agent can tell it apart from tokopedia_search-style siblings.

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?

The description makes it clear that this tool is for autocomplete/partial-keyword use and explicitly warns that results are not product-search results. It does not name a sibling tool to use for full product search results, so the routing guidance is clear but slightly implicit.

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