Skip to main content
Glama
byndcloud

Unofficial Dex CRM MCP Server

by byndcloud

dex_merge_contacts

Merge duplicate contacts in Dex CRM by consolidating multiple entries into a single primary contact with combined data.

Instructions

Merge two or more duplicate contacts into one. The first ID in the group becomes the primary contact that is kept and enriched with data from the others. You can merge multiple groups at once.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contactIdsYesArray of groups to merge — each group is an array of contact IDs (e.g. [['id1','id2']] merges id1 and id2)

Implementation Reference

  • The handler for dex_merge_contacts which performs a POST request to /v1/contacts/merge.
    server.tool(
      "dex_merge_contacts",
      "Merge two or more duplicate contacts into one. The first ID in the group becomes the primary contact that is kept and enriched with data from the others. You can merge multiple groups at once.",
      { contactIds: z.array(z.array(z.string()).min(2)).min(1).describe("Array of groups to merge — each group is an array of contact IDs (e.g. [['id1','id2']] merges id1 and id2)") },
      async (args) => {
        try {
          const result = await dex.post("/v1/contacts/merge", {
            contactIds: args.contactIds,
          });
          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 full burden. It discloses that merging is destructive (first contact kept, others presumably removed) and that data is enriched, but lacks details on permissions needed, rate limits, error handling, or what happens to associated data (e.g., notes, tags). More behavioral context is needed for a mutation tool.

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 sentences with zero waste: the first explains the core functionality, the second adds capability for multiple groups. It's front-loaded with the primary purpose and appropriately sized.

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

Completeness3/5

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

For a destructive mutation tool with no annotations and no output schema, the description is incomplete. It covers the basic operation but lacks critical context like response format, error conditions, side effects on related entities, or confirmation of what 'enriched' entails. More detail is needed given the complexity.

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 the schema fully documents the parameter structure. The description adds marginal value by explaining that the first ID becomes primary and data is merged from others, but doesn't clarify semantics beyond what the schema provides (e.g., order significance, data precedence rules).

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 clearly states the specific action ('merge'), the resource ('duplicate contacts'), and the outcome ('into one'). It distinguishes from siblings like dex_update_contact or dex_delete_contact by focusing on consolidation rather than modification or removal.

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

Usage Guidelines3/5

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

The description implies usage for handling duplicate contacts but doesn't explicitly state when to use this tool versus alternatives like dex_update_contact for modifying a single contact or dex_delete_contact for removing unwanted duplicates. No prerequisites or exclusions are mentioned.

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