Lianex — Australian price comparison

Resolve permalink ids to comparable listings

lianex_resolve_compare

Read-onlyIdempotent

Resolve up to 3 comma-separated product permalink IDs into cached listings for comparison. Each listing includes url, marketplace and item_id, plus title, price and condition when available. Unresolvable IDs and IDs beyond the limit are omitted; an empty set returns listings: []. Cache-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lianex_resolve_compare"
  }
}

Input Schema

Name	Required	Description	Default
`ids`	No	Up to 3 product permalink ids in ONE comma-separated string, e.g. amazon~~B0G2BFZRGL,v1~158082631449~0 — ids from /api/public/products or /api/public/search (MCP tools lianex_products, lianex_search). Extra ids are ignored.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 schema fields changedNov 2, 2026
- removedOutput schema / $defs / CompareListing / description
```
Removed value: -"A resolved cached listing suitable for comparison."
```
- removedOutput schema / $defs / CompareListing / properties / condition / description
```
Removed value: -"Present only when we hold one."
```
- removedOutput schema / $defs / CompareListing / properties / condition / title
```
Removed value: -"Condition"
```
- removedOutput schema / $defs / CompareListing / properties / item_id / description
```
Removed value: -"The marketplace's full id, variation included."
```
- removedOutput schema / $defs / CompareListing / properties / item_id / title
```
Removed value: -"Item Id"
```
- removedOutput schema / $defs / CompareListing / properties / marketplace / description
```
Removed value: -"The registry ROUTING TOKEN (`ebay`, `amazon`, …), not the stored locale label."
```
- removedOutput schema / $defs / CompareListing / properties / marketplace / title
```
Removed value: -"Marketplace"
```
- removedOutput schema / $defs / CompareListing / properties / price / description
```
Removed value: -"Present only when we hold one."
```
- removedOutput schema / $defs / CompareListing / properties / price / title
```
Removed value: -"Price"
```
- removedOutput schema / $defs / CompareListing / properties / title / description
```
Removed value: -"Present only when we hold one."
```
- removedOutput schema / $defs / CompareListing / properties / title / title
```
Removed value: -"Title"
```
- removedOutput schema / $defs / CompareListing / properties / url / description
```
Removed value: -"Affiliate-wrapped outbound link."
```
- removedOutput schema / $defs / CompareListing / properties / url / title
```
Removed value: -"Url"
```
- removedOutput schema / $defs / CompareListing / title
```
Removed value: -"CompareListing"
```
- removedOutput schema / $defs / ResolveCompareResponse / description
```
Removed value: -"Resolved cached listings. Unresolvable IDs and IDs beyond the request limit are omitted; an empty set returns listings: []."
```
- removedOutput schema / $defs / ResolveCompareResponse / properties / listings / title
```
Removed value: -"Listings"
```
- removedOutput schema / $defs / ResolveCompareResponse / title
```
Removed value: -"ResolveCompareResponse"
```
- removedOutput schema / title
```
Removed value: -"Response Resolve Compare Api Public Resolve Compare Get"
```

Changed1 schema field changedOct 29, 2026

addedInput schema / properties / ids / description

Added value: +"Up to 3 product permalink ids in ONE comma-separated string, e.g. amazon~~B0G2BFZRGL,v1~158082631449~0 — ids from /api/public/products or /api/public/search (MCP tools lianex_products, lianex_search). Extra ids are ignored."

First observedOct 22, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, and the description still adds substantive detail: unresolvable and over-limit IDs are silently omitted, an empty set returns listings: [], and results come from cache only. That tells an agent exactly how partial failures and limits manifest, which no structured field provides.

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 short sentences, front-loaded with the core action and limit, followed by output shape and edge-case handling. Every sentence contributes new information with no repetition.

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?

With annotations covering safety semantics and an output schema present, the description only needs to add behavioral edge cases, which it does thoroughly (omission rules, empty-set return, cache-only). Nothing an agent needs to invoke it correctly 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 description coverage is 100%, so the single 'ids' parameter is already fully documented, including the comma-separated format and examples. The description restates the three-ID limit and omission behavior but adds no format or syntax detail beyond the schema, so baseline 3 applies.

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?

The description opens with a specific verb and resource ('Resolve up to 3 comma-separated product permalink IDs into cached listings for comparison') and names the concrete outcome, so an agent can distinguish it from the retrieval siblings like lianex_products and lianex_search. It stops short of explicitly contrasting itself with the comparison siblings (lianex_vs, lianex_vs_by_slug), but the cache-resolution framing is still unambiguous.

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?

'Cache-only' and the three-ID cap give clear operational context, and the schema explains that IDs originate from lianex_products or lianex_search. It doesn't explicitly name a sibling to use instead when IDs are absent or need live fetching, but the usage context is well set.

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

All Lianex — Australian price comparison tools Inspect

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

Need Help?