Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tokopedia_home_tabs

Lists Tokopedia home recommendation tabs, returning each tab's ID and name for loading specific tabs via the /tokopedia/home endpoint.

Instructions

List Tokopedia home recommendation tabs. Lists the current Tokopedia home recommendation tabs, each with its id, name and an optional image URL, plus a fetched_at timestamp. It takes no parameters. Pass a returned id as tab_id to /tokopedia/home to load that tab.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that the tool is parameterless, describes the return fields (`id`, `name`, optional image URL, `fetched_at` timestamp), and explains the downstream flow. It omits any note on pagination, caching, or auth, which for a read-only list is a minor gap.

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?

Three short sentences, front-loaded with the purpose, then return shape, then the routing instruction. Efficient, though sentence two restates 'tabs' from sentence one before adding field detail, a mild redundancy that keeps it from a 5.

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 zero-parameter listing tool with no annotations and no output schema, the description covers purpose, return fields, and downstream usage. The description compensates for the absent output schema by enumerating the returned fields. Only minor omissions (ordering, snapshot semantics of `fetched_at`) remain.

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?

The tool has zero parameters, so the baseline is 4. The description correctly confirms 'It takes no parameters,' matching the empty schema, and adds the consumer-side meaning of the returned `id` via `tab_id`.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

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

States a specific verb+resource ('List Tokopedia home recommendation tabs') and reinforces the scope by naming the endpoint the IDs feed into ('/tokopedia/home'). It is clearly distinguishable from tokopedia_home and tokopedia_search by framing itself as the tab discovery step. It stops short of naming a sibling explicitly, so not quite a 5.

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?

Gives concrete usage context: it takes no parameters, and a returned `id` should be passed as `tab_id` to `/tokopedia/home`. That is an actionable workflow instruction an agent can follow directly. It does not state when-not-to-use it or name alternative siblings, so it falls below an explicit 5.

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