Skip to main content
Glama

Lianex — Australian price comparison

Cached products in one published category

lianex_browse_by_slug
Read-onlyIdempotent

Return ranked cached products for a published category. Unknown or unpublished slugs return 404. A renamed slug returns 200 with redirect_to; request that current slug. An empty category returns found: false, noindex: true and products: []. Otherwise found is true; total counts the products in this response, not all marketplace matches. Cache-only.

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": {
      "slug": "<slug>"
    },
    "name": "lianex_browse_by_slug"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesA published browse category slug, e.g. mobile-phones — the slug of an entry from /api/public/browse (MCP tool lianex_browse).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed54 schema fields changed
    • removedOutput schema / $defs / BrowseCard / description
      Removed value: -"A ranked category product card. Its fields differ from product detail; offers is a count of grouped offers."
    • removedOutput schema / $defs / BrowseCard / properties / badges / description
      Removed value: -"Display badges the ranker assigned."
    • removedOutput schema / $defs / BrowseCard / properties / badges / title
      Removed value: -"Badges"
    • removedOutput schema / $defs / BrowseCard / properties / bucket / description
      Removed value: -"The condition bucket this card landed in."
    • removedOutput schema / $defs / BrowseCard / properties / bucket / title
      Removed value: -"Bucket"
    • removedOutput schema / $defs / BrowseCard / properties / condition / title
      Removed value: -"Condition"
    • removedOutput schema / $defs / BrowseCard / properties / currency / title
      Removed value: -"Currency"
    • removedOutput schema / $defs / BrowseCard / properties / from_price / description
      Removed value: -"Lowest price across the grouped offers."
    • removedOutput schema / $defs / BrowseCard / properties / from_price / title
      Removed value: -"From Price"
    • removedOutput schema / $defs / BrowseCard / properties / image / description
      Removed value: -"Primary image URL."
    • removedOutput schema / $defs / BrowseCard / properties / image / title
      Removed value: -"Image"
    • removedOutput schema / $defs / BrowseCard / properties / item_id / title
      Removed value: -"Item Id"
    • removedOutput schema / $defs / BrowseCard / properties / offers / description
      Removed value: -"Number of grouped offers represented by this card. Product detail instead uses offers for a list."
    • removedOutput schema / $defs / BrowseCard / properties / offers / title
      Removed value: -"Offers"
    • removedOutput schema / $defs / BrowseCard / properties / price / title
      Removed value: -"Price"
    • removedOutput schema / $defs / BrowseCard / properties / provider / description
      Removed value: -"The marketplace routing token — build the `/p/` permalink from it. Added by the endpoint, not by the card projection."
    • removedOutput schema / $defs / BrowseCard / properties / provider / title
      Removed value: -"Provider"
    • removedOutput schema / $defs / BrowseCard / properties / reason / description
      Removed value: -"Why the ranker placed this card here."
    • removedOutput schema / $defs / BrowseCard / properties / reason / title
      Removed value: -"Reason"
    • removedOutput schema / $defs / BrowseCard / properties / title / title
      Removed value: -"Title"
    • removedOutput schema / $defs / BrowseCard / properties / url / description
      Removed value: -"Affiliate-wrapped outbound link."
    • removedOutput schema / $defs / BrowseCard / properties / url / title
      Removed value: -"Url"
    • removedOutput schema / $defs / BrowseCard / title
      Removed value: -"BrowseCard"
    • removedOutput schema / $defs / BrowseCategoryPage / description
      Removed value: -"Cached products for a published category. found: false means no cached products are available; products is empty and noindex is true."
    • removedOutput schema / $defs / BrowseCategoryPage / properties / category_id / title
      Removed value: -"Category Id"
    • removedOutput schema / $defs / BrowseCategoryPage / properties / description / title
      Removed value: -"Description"
    • removedOutput schema / $defs / BrowseCategoryPage / properties / found / description
      Removed value: -"`false` means we hold NO cached listings — not that the category is unknown."
    • removedOutput schema / $defs / BrowseCategoryPage / properties / found / title
      Removed value: -"Found"
    • removedOutput schema / $defs / BrowseCategoryPage / properties / h1 / description
      Removed value: -"The page's H1, which may be a keyword-intent variant of `name`."
    • removedOutput schema / $defs / BrowseCategoryPage / properties / h1 / title
      Removed value: -"H1"
    • removedOutput schema / $defs / BrowseCategoryPage / properties / name / title
      Removed value: -"Name"
    • removedOutput schema / $defs / BrowseCategoryPage / properties / noindex / description
      Removed value: -"`true` on the soft-empty page, so it is never indexed."
    • removedOutput schema / $defs / BrowseCategoryPage / properties / noindex / title
      Removed value: -"Noindex"
    • removedOutput schema / $defs / BrowseCategoryPage / properties / products / description
      Removed value: -"The ranked cached cards, or `[]`."
    • removedOutput schema / $defs / BrowseCategoryPage / properties / products / title
      Removed value: -"Products"
    • removedOutput schema / $defs / BrowseCategoryPage / properties / qualifier / description
      Removed value: -"The page's keyword qualifier within its category (e.g. `gaming`), or empty for a whole-category page. The in-app Browse hand-off sends the category id plus only this text."
    • removedOutput schema / $defs / BrowseCategoryPage / properties / qualifier / title
      Removed value: -"Qualifier"
    • removedOutput schema / $defs / BrowseCategoryPage / properties / siblings / description
      Removed value: -"The other published categories, for nav."
    • removedOutput schema / $defs / BrowseCategoryPage / properties / siblings / title
      Removed value: -"Siblings"
    • removedOutput schema / $defs / BrowseCategoryPage / properties / slug / title
      Removed value: -"Slug"
    • removedOutput schema / $defs / BrowseCategoryPage / properties / title / title
      Removed value: -"Title"
    • removedOutput schema / $defs / BrowseCategoryPage / properties / total / description
      Removed value: -"Number of products in this response, not a catalogue-wide match total."
    • removedOutput schema / $defs / BrowseCategoryPage / properties / total / title
      Removed value: -"Total"
    • removedOutput schema / $defs / BrowseCategoryPage / properties / updated_at / description
      Removed value: -"Freshest cached listing in the category, or `null`."
    • removedOutput schema / $defs / BrowseCategoryPage / properties / updated_at / title
      Removed value: -"Updated At"
    • removedOutput schema / $defs / BrowseCategoryPage / title
      Removed value: -"BrowseCategoryPage"
    • removedOutput schema / $defs / BrowseSibling / properties / name / title
      Removed value: -"Name"
    • removedOutput schema / $defs / BrowseSibling / properties / slug / title
      Removed value: -"Slug"
    • removedOutput schema / $defs / BrowseSibling / title
      Removed value: -"BrowseSibling"
    • removedOutput schema / $defs / SlugRedirect / description
      Removed value: -"The requested address has a current canonical slug. This JSON response uses status 200. Request the returned slug on the same endpoint."
    • removedOutput schema / $defs / SlugRedirect / properties / redirect_to / description
      Removed value: -"The slug to follow. Not a URL — a slug."
    • removedOutput schema / $defs / SlugRedirect / properties / redirect_to / title
      Removed value: -"Redirect To"
    • removedOutput schema / $defs / SlugRedirect / title
      Removed value: -"SlugRedirect"
    • removedOutput schema / title
      Removed value: -"Response 200 Public Browse Category Api Public Browse  Slug  Get"
  2. Changed1 schema field changed
    • addedInput schema / properties / slug / description
      Added value: +"A published browse category slug, e.g. mobile-phones — the slug of an entry from /api/public/browse (MCP tool lianex_browse)."
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, closed-world), and the description adds the non-obvious behavior: 404 on unpublished slugs, redirect semantics on renames, the exact empty-category shape, the meaning of total, and that results are cache-only. This is exactly the context annotations cannot convey and is consistent with openWorldHint=false.

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?

Six short sentences, no filler. The core action leads, then failure modes, then return semantics — each sentence carries a distinct, actionable fact.

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?

Even though an output schema exists, the description explains the response flags (found, noindex, total) that an agent must interpret correctly and closes with the cache-only caveat. Nothing needed to call it correctly is missing.

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?

Schema coverage is 100% and the single required slug is already described with an example and a pointer to lianex_browse as its source. The description still adds meaning by establishing that only *published* slugs are valid and that stale slugs redirect rather than fail, which goes beyond the schema text.

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 with scope: 'Return ranked cached products for a published category.' The word 'cached' plus 'published category' separates it from the live-search siblings (lianex_search, lianex_products) and from lianex_browse, which enumerates categories rather than their products.

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 outcome handling: unknown/unpublished slug → 404, renamed slug → 200 with redirect_to and re-request the current slug, empty category → found: false. It never explicitly names an alternative tool for fresh (non-cached) data, so the when-not guidance is implied rather than stated.

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.

Resources