Chatway Live Chat

Remove Contact Tag

remove-tag

Destructive

Remove a named tag from the visitor/contact associated with a Chatway conversation. Use list-tags to check the exact tag name.

Input Schema

Name	Required	Description	Default
`name`	Yes	Exact name of the tag to remove.
`conversation_id`	Yes	UUID of the conversation whose visitor/contact the tag is removed from.

Output Schema

Name	Required	Description
`removed_tag`	No	Name of the removed tag.
`chat_contact_id`	No	Visitor/contact UUID the tag was removed from.
`conversation_id`	No	Conversation UUID.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 6, 2026

removedInput schema / properties / confirmation_token

Removed value: -{
-  "description": "Required after the confirmation challenge. Ask the user to approve before calling again with this token.",
-  "type": "string"
-}

removedOutput schema / properties / affected_count

Removed value: -{
-  "description": "Number of records the action will change.",
-  "type": "integer"
-}

removedOutput schema / properties / confirmation_required

Removed value: -{
-  "description": "True when the user must approve before the action runs.",
-  "type": "boolean"
-}

removedOutput schema / properties / confirmation_token

Removed value: -{
-  "description": "Pass back as confirmation_token after the user approves.",
-  "type": "string"
-}

removedOutput schema / properties / expires_in_seconds

Removed value: -{
-  "description": "How long the confirmation token stays valid.",
-  "type": "integer"
-}

removedOutput schema / properties / message

Removed value: -{
-  "description": "Message describing the action or its result.",
-  "type": "string"
-}

Changed4 schema fields changedOct 15, 2026

addedInput schema / properties / confirmation_token / description

Added value: +"Required after the confirmation challenge. Ask the user to approve before calling again with this token."

addedInput schema / properties / conversation_id / description

Added value: +"UUID of the conversation whose visitor/contact the tag is removed from."

addedInput schema / properties / name / description

Added value: +"Exact name of the tag to remove."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "affected_count": {
+      "description": "Number of records the action will change.",
+      "type": "integer"
+    },
+    "chat_contact_id": {
+      "description": "Visitor/contact UUID the tag was removed from.",
+      "type": "string"
+    },
+    "confirmation_required": {
+      "description": "True when the user must approve before the action runs.",
+      "type": "boolean"
+    },
+    "confirmation_token": {
+      "description": "Pass back as confirmation_token after the user approves.",
+      "type": "string"
+    },
+    "conversation_id": {
+      "description": "Conversation UUID.",
+      "type": "string"
+    },
+    "expires_in_seconds": {
+      "description": "How long the confirmation token stays valid.",
+      "type": "integer"
+    },
+    "message": {
+      "description": "Message describing the action or its result.",
+      "type": "string"
+    },
+    "removed_tag": {
+      "description": "Name of the removed tag.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 15, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=false, so the risk profile is covered structurally. The description adds useful scoping (the tag is removed from the conversation's visitor/contact), but says nothing about what happens if the named tag does not exist (error vs. silent no-op).

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 short sentences, zero filler, and the core action is front-loaded before the prerequisite hint. Nothing could be removed without losing information.

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?

With only two required parameters, full schema coverage, an output schema, and annotations covering destructiveness, the description is nearly sufficient. The only meaningful gap is the behavior on a non-existent tag name, which matters for a destructive mutation.

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%, so both parameters are already documented, establishing a baseline of 3. The description's pointer to `list-tags` for the exact tag name adds a small amount of practical meaning about the `name` parameter's expected precision.

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 ('Remove a named tag') and scopes it precisely to 'the visitor/contact associated with a Chatway conversation', which cleanly separates it from the add-tag sibling. An agent can identify the operation without opening the 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?

It gives a concrete prerequisite: use `list-tags` to check the exact tag name before removing. That is actionable routing guidance, but there is no explicit exclusion such as what to do when the tag is absent from the contact.

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

All Chatway Live Chat 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?