Surface AI

Set a variant's status

variant_set_status

DestructiveIdempotent

Activate, pause or archive a variant. Only active variants are served. To change which variant is the control, use variant_set_control.

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": {
      "surface_id": "<surface_id>",
      "variant_id": "<variant_id>",
      "status": "<status>"
    },
    "name": "variant_set_status"
  }
}

Input Schema

Name	Required	Description
`status`	Yes	ACTIVE serves it; PAUSED and ARCHIVED stop serving it.
`surface_id`	Yes	The surface id, from surface_list.
`variant_id`	Yes	The variant id, from variant_list.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 12, 2026

addedInput schema / properties / status / description

Added value: +"ACTIVE serves it; PAUSED and ARCHIVED stop serving it."

changedInput schema / properties / surface_id / description

Previous value: -"The surface id."New value: +"The surface id, from surface_list."

First observedNov 11, 2026

TDQS

A4/5.0

Behavior3/5

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

The annotations already declare this is a mutating, destructive, idempotent operation, and the description adds the real behavioral consequence that only ACTIVE variants are served. However, it does not state whether ARCHIVED is reversible or whether archiving removes data/history — a meaningful gap for a tool flagged destructiveHint=true.

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 with no filler: the action first, the serving consequence second, the sibling redirect last. Nothing is repeated unnecessarily and the most decision-relevant fact is front-loaded.

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 simple three-parameter mutation with full schema coverage, full annotations, and no output schema, the description covers purpose, effect, and the main alternative. The only missing piece an agent would want is the consequence/reversibility of ARCHIVED.

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 coverage is 100% and the status enum is already documented in the schema with the same ACTIVE/PAUSED/ARCHIVED serving distinction. The description restates that serving rule but adds no new meaning, such as the difference in reversibility between PAUSED and ARCHIVED or constraints on surface_id/variant_id pairing.

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 set (activate, pause, archive) on a specific resource (a variant) and immediately states the operative consequence: 'Only active variants are served.' It also explicitly distinguishes itself from variant_set_control, so an agent can route correctly without opening either schema.

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?

Usage is clearly implied by the effect statement — call this whenever a variant's serving state must change — and the description explicitly hands the control-selection case to variant_set_control. It does not cover adjacent cases such as when to prefer variant_update versus this tool, so it stops short of full when/when-not guidance.

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

All Surface AI 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?