Skip to main content
Glama

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).

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": "offers_update_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoAccount id from list_accounts. Optional when only one account is connected.
changesNo
changes_urlNoInstead of changes: a .json file under https://vendwiser.ai/media/ with the same list of changes, for long batches (100 per call; changes_from 0, 100, 200 … for the next ones).
changes_fromNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / changes_from
      Added value: +{
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / changes_url
      Added value: +{
      +  "description": "Instead of changes: a .json file under https://vendwiser.ai/media/ with the same list of changes, for long batches (100 per call; changes_from 0, 100, 200 … for the next ones).",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "changes"
      -]New value: +[]
  2. 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"
      +}
  3. 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."
  4. 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"
      +}
  5. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that the operation is simulated first, nothing changes until the seller approves, and the marketplace reviews content changes before showing them. It also explains that blocking marketplace or seller rules cause refusal, which is important behavioral context for a non-destructive mutation tool.

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 prerequisite workflow is front-loaded, followed by scope, behavior, and environment notes. The description is dense but well organized; some parenthetical platform details add length, but most sentences earn their place.

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 complex multi-field proposal tool with an output schema, the description covers the critical workflow, approval behavior, and most field semantics. It still lacks explicit guidance on batch changes versus direct changes and on the delivery-days overlap with the handling-time sibling.

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?

With only 50% schema description coverage, the description adds useful meaning: attributes are by name/value as offers_content_get shows them, images replaces the list while images_add appends, and description_replace edits exact fragments. It does not explain account, changes_url, changes_from, or several eMAG-specific fields, leaving those to the schema.

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 states a specific verb and resource: "Propose changes to product pages," then enumerates the editable content types (title, description, attributes, pictures, delivery days). This clearly separates it from siblings that update price, stock, status, or handling time.

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 gives explicit prerequisites: call listing_guide before writing a title or description, and listing_check on the draft, with blocking findings causing refusal. It does not clarify how delivery_days here relates to the sibling offers_update_handling_time, or when to use changes_url versus changes, so guidance is strong but not complete.

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