Skip to main content
Glama

Vendwiser

by ai.vendwiser
OverviewDiscussionsAdmin

Propose product content changes

offers_update_content

[Catalog changes] Call listing_guide before writing a new title or description and listing_check on the draft: a change with a blocking finding (marketplace rule or the seller's house rule) is refused here. Propose changes to product pages: title, description (whole, or find-and-replace inside the current one), attributes (by name and value, as offers_content_get shows them), pictures (images replaces the list, images_add appends; Amazon, eMAG, Trendyol) and delivery days. Simulated first; nothing changes until the seller approves. The marketplace reviews content changes before showing them. Works on: Demo shop (sample data).

Input Schema

NameRequiredDescriptionDefault
accountNoAccount id from list_accounts. Optional when only one account is connected.
changesYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / changes / items / properties / images / description
      Previous value: -"Amazon and eMAG: public https addresses of the pictures, the main one first; replaces the current ones."New value: +"Amazon, eMAG and Trendyol: public https addresses of the pictures, the main one first; replaces the current ones (Trendyol: at most 8, 1200 x 1800 px portrait; only this barcode's page unless whole_product is true)."
    • addedInput schema / properties / changes / items / properties / images_add
      Added value: +{
+  "description": "Trendyol: pictures added after the current ones (public https addresses).",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 8,
+  "type": "array"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / changes / items / properties / images / description
      Previous value: -"Amazon only: public https addresses of the pictures, the main one first; replaces the current ones."New value: +"Amazon and eMAG: public https addresses of the pictures, the main one first; replaces the current ones."
  3. Changed6 schema fields changed
    • changedInput schema / properties / changes / items / properties / bullet_points / description
      Previous value: -"Temu only: the short selling points shown above the description."New value: +"Temu and Amazon: the short selling points shown above the description."
    • addedInput schema / properties / changes / items / properties / family_id
      Added value: +{
+  "description": "eMAG only, with product_main_id: join an existing family by its id (offers_get shows it on a sibling size).",
+  "type": [
+    "integer",
+    "string"
+  ]
+}
    • addedInput schema / properties / changes / items / properties / family_type
      Added value: +{
+  "description": "eMAG only, with product_main_id: the family type (for example Dimensiune); default the size-like one of the category.",
+  "type": "string"
+}
    • addedInput schema / properties / changes / items / properties / images
      Added value: +{
+  "description": "Amazon only: public https addresses of the pictures, the main one first; replaces the current ones.",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 9,
+  "type": "array"
+}
    • addedInput schema / properties / changes / items / properties / product_main_id
      Added value: +{
+  "description": "eMAG only: the family name that ties the sizes of one product together on one page; give the same value on every size. An existing family id is kept when the name matches.",
+  "type": "string"
+}
    • addedInput schema / properties / changes / items / properties / vat_rate
      Added value: +{
+  "description": "eMAG only: the VAT rate of the offer in percent (for example 21); vat_list shows the rates the account has.",
+  "type": "number"
+}
  4. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses that changes are simulated first, nothing changes until seller approval, the marketplace reviews content changes, and blocking rule findings cause refusal. This is exactly the kind of behavioral context that annotations alone cannot provide.

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?

The information is front-loaded and every sentence contributes, but some sentences are dense and pack multiple clauses (e.g., the images sentence). It remains readable and efficient overall.

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?

Given an output schema exists and annotations cover safety, the description still supplies the critical workflow context: prerequisite validations, simulation, approval gate, marketplace review, and supported platforms. Nothing essential is missing for an agent to call it correctly.

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?

It adds useful semantics for key parameters: description can be whole or find-and-replace, attributes are by name/value as offers_content_get shows them, images replaces the list while images_add appends, and platform restrictions are noted. The schema itself already has detailed nested descriptions, so this is complementary rather than essential.

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?

The description names a specific verb ('Propose changes') and a precise resource ('product pages') and enumerates the exact fields that can change. It clearly distinguishes this from sibling tools like offers_update_price, offers_update_stock, or offers_create.

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?

It states important prerequisites: call listing_guide before writing a title/description and listing_check on the draft, and that blocking findings cause refusal. It also explains the simulation and seller-approval workflow. It does not explicitly name alternatives for non-content updates, but the domain is clear.

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

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