Unofficial Dex CRM MCP Server

dex_create_tag

Create a new tag with a name and optional color to categorize and organize contacts in your CRM system.

Instructions

Create a new tag with a name and optional color for categorizing contacts.

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": {
      "name": "<name>"
    },
    "name": "dex_create_tag"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`color`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 23, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It states this is a creation tool, implying mutation, but doesn't disclose behavioral traits like required permissions, whether the tag is immediately available, if duplicates are allowed, or what happens on failure. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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?

The description is a single, efficient sentence with zero waste. It front-loads the purpose ('Create a new tag') and adds necessary details (parameters and context) concisely. Every word earns its place, making it easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (mutation with 2 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like permissions or error handling, and while it mentions parameters, it lacks details on formats or constraints. For a creation tool, this leaves critical gaps in context.

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 0%, so the description must compensate. It adds meaning by specifying that 'name' and 'color' are for the tag, with 'color' being optional, which clarifies beyond the bare schema. However, it doesn't explain parameter formats (e.g., color codes), constraints, or examples, leaving gaps in semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Create a new tag') and the resource ('tag'), specifying it's for categorizing contacts. It distinguishes from sibling tools like dex_update_tag or dex_delete_tag by focusing on creation. However, it doesn't explicitly differentiate from other creation tools like dex_create_group or dex_create_custom_field beyond the resource type.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, when not to use it, or compare it to sibling tools like dex_manage_contact_tags or dex_update_tag for similar functionality. Usage is implied only by the action and resource.

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