Chatway Live Chat

Add Contact Tag

add-tag

Attach a named tag to the visitor/contact associated with a Chatway conversation. If supported by Chatway, the tag may be created when it does not already exist. Use view-tags first to reuse an existing tag name, and remove-tag to undo.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Tag name, up to 100 characters. An existing tag with this name is reused; otherwise a new tag is created.
`color`	No	Optional tag color, up to 50 characters (for example a hex code such as #2563EB). If the tag already exists, its color is changed to this value.
`conversation_id`	Yes	UUID of the conversation; the tag is attached to its visitor/contact.

Output Schema

TableJSON Schema

Name	Required	Description
`tag`	No	Tag name.
`chat_contact_id`	No	Visitor/contact UUID the tag was attached to.
`conversation_id`	No	Conversation UUID.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 15, 2026

addedInput schema / properties / color / description

Added value: +"Optional tag color, up to 50 characters (for example a hex code such as #2563EB). If the tag already exists, its color is changed to this value."

addedInput schema / properties / conversation_id / description

Added value: +"UUID of the conversation; the tag is attached to its visitor/contact."

addedInput schema / properties / name / description

Added value: +"Tag name, up to 100 characters. An existing tag with this name is reused; otherwise a new tag is created."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "chat_contact_id": {
+      "description": "Visitor/contact UUID the tag was attached to.",
+      "type": "string"
+    },
+    "conversation_id": {
+      "description": "Conversation UUID.",
+      "type": "string"
+    },
+    "tag": {
+      "description": "Tag name.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 15, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the bar is lower. The description still adds real behavioral nuance beyond them: tag creation is conditional ('If supported by Chatway, the tag may be created'), existing names are reused rather than duplicated, and the effect is reversible via remove-tag. It says nothing about permission requirements or failure modes, which keeps it out of 5 territory.

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 tight sentences, front-loaded with the core action and its target, followed by the creation caveat and the sibling routing. No filler or restated field names.

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?

An output schema exists, so return values need not be described, and with only three fully documented parameters the description's job is the reuse/undo workflow, which it covers. Enough for an agent to call this correctly without further lookup.

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 documents name, color (including the color-change-on-existing-tag behavior), and conversation_id's UUID semantics. The description adds no format, constraint, or default detail beyond the schema, 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?

States a specific verb+resource ('Attach a named tag') and names the exact target ('the visitor/contact associated with a Chatway conversation'), which is not obvious from the name alone. It also distinguishes itself from siblings by naming view-tags and remove-tag, so an agent can place it in the tagging workflow without opening a 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?

Gives explicit ordering guidance ('Use view-tags first to reuse an existing tag name') and a rollback path ('remove-tag to undo'), which routes the agent to the correct siblings. It stops short of stating when not to tag or what prerequisites (permissions, conversation state) must hold.

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?