campaignstack

campaignstack_revert_voice

Restore a previous version of a voice profile. Call this when the user picks a specific versionId from campaignstack_list_voice_versions, typically after a re-extraction made the voice worse and they want the earlier one back. The current state is snapshotted first and the profile's version number goes UP, because a version is a write counter rather than a pointer into the history.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`versionId`	Yes	versionId from campaignstack_list_voice_versions.
`workspaceId`	No	Workspace ID. REQUIRED for a user key (csu_), which spans every workspace you belong to; omitted for a workspace key (cs_), which is bound to one and ignores this argument. campaignstack_whoami reports which kind of key you are holding and, for a user key, the workspaces it can reach.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`version`	No
`language`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "language": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "string"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "version": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "number"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "type": "object"
+}

AddedSep 13, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only say the tool is not read-only and not idempotent. The description adds non-obvious behavior: the current state is snapshotted first and the profile's version number goes UP because a version is a write counter rather than a history pointer. This prevents a serious misinterpretation of what 'revert' means.

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 sentences with no filler. The action is front-loaded, the trigger condition is clearly stated, and the critical version-counter caveat earns its place in the final sentence.

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 mutation tool with one required parameter, the description explains the operation, the trigger context, and the non-obvious versioning semantics. With an output schema present and detailed parameter schemas, nothing essential is missing for an agent to invoke it correctly.

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%, and the schema already explains versionId as coming from campaignstack_list_voice_versions and documents the workspaceId user-key/workspace-key nuance thoroughly. The description adds no parameter detail beyond what the schema provides, so the baseline 3 applies.

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 opens with a specific verb and resource: 'Restore a previous version of a voice profile.' It names the exact upstream tool (campaignstack_list_voice_versions) and clearly distinguishes itself from sibling revert tools like campaignstack_revert_guidance and campaignstack_revert_playbook.

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?

The description says explicitly when to call this tool: 'Call this when the user picks a specific versionId from campaignstack_list_voice_versions, typically after a re-extraction made the voice worse and they want the earlier one back.' This gives the agent a concrete trigger condition and the user intent that warrants invocation.

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

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