Vendwiser

List offers

offers_list

Read-onlyIdempotent

[Catalog] One page of offers (up to 100), each with price, stock, status, buy-button rank and handling time. To find or count offers that match something (a word in the name, a SKU prefix, stock, price, handling time, rejected, buy button lost), call offers_find ONCE instead of paging through this list: every page here is a separate call. Never call offers_get once per offer. List the seller's offers with price, stock, status, validation state and buy-button position. On eMAG prices are WITHOUT VAT (the shopper sees price plus VAT; use vat_list for the rate). On Trendyol prices INCLUDE VAT (price_includes_vat is true). Works on: Demo shop (sample data).

Input Schema

Name	Required	Description
`sku`	No	Exact seller SKU (part number).
`page`	No	Page number, starting at 1.
`status`	No	incomplete (Temu only): variants Temu holds back until their product is completed.
`account`	No	Account id from list_accounts. Optional when only one account is connected.
`per_page`	No	Items per page (default 50, max 100).
`page_token`	No	Temu, status incomplete: next_page_token of the previous page.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 12, 2026

addedInput schema / properties / page_token

Added value: +{
+  "description": "Temu, status incomplete: next_page_token of the previous page.",
+  "type": "string"
+}

addedInput schema / properties / status / description

Added value: +"incomplete (Temu only): variants Temu holds back until their product is completed."

changedInput schema / properties / status / enum

Previous value: -[
-  "active",
-  "inactive"
-]New value: +[
+  "active",
+  "inactive",
+  "incomplete"
+]

First observedOct 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive, so the description's job is added context — and it delivers the high-value, non-obvious trait that eMAG prices exclude VAT while Trendyol prices include it. It stops short of any error behavior, rate limits, or guaranteed ordering, which keeps it off a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded and useful, but the payload list is stated twice in different words ('price, stock, status, buy-button rank and handling time' then 'price, stock, status, validation state and buy-button position'), and the 'Works on: Demo shop (sample data)' tail adds little. Tightening would gain a level.

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 an output schema present the description needn't explain return values, and the parameter schema is complete, so the essentials are covered. The remaining gap is paging mechanics across marketplaces (page_token is Temu-only per the schema), which the description never reconciles with its 'page through this list' warning.

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 sku, page, status, account, per_page and page_token are already documented; baseline 3 applies. The description adds the VAT interpretation of the returned price fields but nothing new about the parameters themselves.

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+resource (list offers), the page size bound, and exactly what each record carries (price, stock, status, buy-button rank, handling time). It also distinguishes itself from offers_find and offers_get by name, so an agent can route without opening any other schema.

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?

Explicit exclusions with the alternative named: for matching/counting use offers_find ONCE instead of paging, and never call offers_get once per offer. It even gives the reason (every page is a separate call), which is exactly what an agent needs to avoid an N-call loop.

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

All Vendwiser 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?