Skip to main content
Glama
byndcloud

Unofficial Dex CRM MCP Server

by byndcloud

dex_update_tag

Modify tag names and colors in Dex CRM to organize contacts and improve data management.

Instructions

Update a tag's name or color by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagIdYes
nameNo
colorNo

Implementation Reference

  • The implementation of the 'dex_update_tag' tool, which handles updating a tag's name or color by its ID via a PUT request to the dex client.
    server.tool(
      "dex_update_tag",
      "Update a tag's name or color by ID.",
      {
        tagId: z.string(),
        name: z.string().optional(),
        color: z.string().optional(),
      },
      async (args) => {
        try {
          const result = await dex.put(`/v1/tags/${args.tagId}`, {
            tag: { name: args.name, color: args.color },
          });
          return toResult(result);
        } catch (error) {
          return toError(error);
        }
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it's an update operation, implying mutation, but lacks details on permissions, side effects, error handling, or response format. This is inadequate for a mutation tool with zero annotation coverage.

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 no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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?

For a mutation tool with no annotations, no output schema, and 0% schema description coverage, the description is insufficient. It lacks critical information such as what the tool returns, error conditions, or behavioral nuances, leaving significant gaps for an AI agent to use 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?

The description mentions updating 'name or color by ID,' which aligns with the three parameters (tagId, name, color) but adds minimal semantics beyond the schema. With 0% schema description coverage, it partially compensates by indicating what fields can be updated, but doesn't explain parameter formats or constraints.

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 ('Update') and resource ('a tag's name or color by ID'), making the purpose understandable. It distinguishes from sibling tools like 'dex_create_tag' and 'dex_delete_tag' by specifying it's for updates, though it doesn't explicitly contrast with other update tools like 'dex_update_contact'.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing tag ID), exclusions, or comparisons to similar tools like 'dex_manage_contact_tags' for tag-related operations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/byndcloud/unofficial-dex-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server