Skip to main content
Glama
A1 Yandex KIT MCP

A1 Yandex KIT MCP

Archive or unarchive variant

variant_action

Archives a product variant to hide it from the storefront while keeping it restorable, or unarchives it to set status to hidden for later publishing.

Instructions

Archive a variant (soft delete: status becomes ARCHIVED, item is hidden from the storefront but restorable) or unarchive it (status becomes HIDDEN; publish it afterwards via update_variant). Success ({"ok":true}) only means the request was processed: for an unknown id or a transition that does not apply the API also answers 204 and changes nothing — confirm the new status with get_variant.

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": {
      "id": "<id>",
      "action": "<action>"
    },
    "name": "variant_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesVariant ID (UUID).
actionYesAction to perform.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.9/5.0
Behavior5/5

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

No annotations are supplied, yet the description carries the full burden: archive is a soft delete that hides from the storefront while remaining restorable, and the response contract is disclosed. Crucially, it warns that a 204/{"ok":true} does not guarantee a state change for unknown ids or inapplicable transitions, which is exactly the silent-failure behavior an agent needs to know.

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?

Two sentences, front-loaded with the operation semantics before the failure-mode caveat. Despite being dense, every clause carries actionable information (status outcome, restorability, verification path) with no restatement of the tool name.

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?

For a two-parameter mutation tool with no annotations and no output schema, the description covers the state transitions, the response payload, the no-op failure mode, and the follow-up verification. Nothing an agent needs in order to call it correctly and interpret the result 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%, so the schema already documents both parameters, setting a baseline of 3. The description adds real meaning on top by mapping each enum value to its resulting status (archive to ARCHIVED, unarchive to HIDDEN) and by explaining how an invalid id behaves for the id parameter.

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 specifies a concrete pair of operations (archive/unarchive) on a concrete resource (variant) and defines what each does in state terms (ARCHIVED vs HIDDEN). It is easily distinguished from siblings like update_variant (used to publish) and get_variant (used to confirm).

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?

It explicitly tells the agent which action to pick and what follows each: after unarchive the item is HIDDEN and must be published via update_variant. It also names get_variant as the required verification step, so the usage path is fully spelled out rather than implied.

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

Deploy Server

Other Tools