Skip to main content
Glama

shopee_suggest

Read-only

Search a partial Shopee keyword and return Shopee's own autocomplete suggestion strings for that storefront. keyword is required and region selects the storefront (my, sg, id, th, vn, ph, tw, br, mx, co, or cl, default my). Use it for plain typeahead completion; prefer shopee_search_hints when ranked hints with category ids and positions are needed.

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": {
      "keyword": "<keyword>"
    },
    "name": "shopee_suggest"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoOptional Shopee storefront region: my, sg, id, th, vn, ph, tw, br, mx, co, or cl. Defaults to my.
keywordYesRequired search keyword prefix to expand, for example head for headphones.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already mark it read-only and open-world, and the description adds useful context that the result is Shopee's own autocomplete strings scoped by storefront. It does not discuss limitations or response shape, but the output schema and annotations cover much of that.

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?

Three tightly packed sentences with no filler. The core purpose is front-loaded, followed by required parameter behavior and the sibling-tool alternative.

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?

Given the simple two-parameter schema, full schema descriptions, annotations, and an output schema, the description covers what the tool does, how it differs from the sibling, and the storefront scoping behavior. Nothing essential is missing.

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%, with both keyword and region fully described, including the region default and allowed values. The description repeats the same essential parameter semantics rather than adding format or edge-case guidance beyond the schema.

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: search a partial Shopee keyword and return Shopee's autocomplete suggestion strings. It also scopes results to a storefront, making the tool's purpose unambiguous.

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 says to use it for plain typeahead completion and names the alternative, shopee_search_hints, for ranked hints with category ids and positions. This gives a clear when-to-use and when-to-prefer-another-tool rule.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.