Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

tokopedia_product

Read-only

Fetch Tokopedia product details from a canonical shop domain and product key, including identity, price, description, and images. Use tokopedia_search to find products.

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": {
      "ShopDomain": "<ShopDomain>",
      "ProductKey": "<ProductKey>"
    },
    "name": "tokopedia_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
ProductKeyYesCanonical Tokopedia product key
ShopDomainYesCanonical Tokopedia shop domain

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. Changed2 schema fields changed
    • addedInput schema / properties / ProductKey / description
      Added value: +"Canonical Tokopedia product key"
    • addedInput schema / properties / ShopDomain / description
      Added value: +"Canonical Tokopedia shop domain"
  2. First observed

TDQS

A4/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, so the safety and network profile is covered. The description adds the payload scope (identity, price, description, images), which is useful, but says nothing about failures, availability, or rate limits beyond what the annotations and output schema provide.

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 sentences, zero filler, with the core fetch behavior front-loaded and the disambiguation placed last. 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?

With a complete input schema, an output schema, and read-only/open-world annotations, the description covers what an agent needs to call it correctly. Only the sourcing of the canonical identifiers is left implicit, a minor gap.

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 description coverage is 100% and both parameters are required and documented, so the schema carries the load. The description only echoes 'canonical shop domain and product key' without adding format or sourcing guidance, so baseline 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?

States a specific verb (Fetch) and resource (Tokopedia product details) and enumerates the returned content (identity, price, description, images). It also names tokopedia_search, so an agent can distinguish it from the search sibling without opening either schema.

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 second sentence routes the agent explicitly: 'Use tokopedia_search to find products,' establishing the search-vs-detail boundary. It does not spell out prerequisites for the two required canonical inputs (where to obtain a shop domain or product key), so it stops short of a full 5.

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

All Crawlora MCP toolsInspect
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