Skip to main content
Glama
cognigy-ai-mcp-management-server

cognigy-ai-mcp-management-server

merge_contact_profiles

Merge a Cognigy.AI contact profile into a target profile, combining their data and contact IDs when the same user has multiple profiles. Set dryRun=false to apply; default validates only.

Instructions

Merges the Cognigy.AI contact profile of a given contact ID into a target profile, combining their data and contact IDs. Use when the same user has multiple profiles. MUTATING: Set dryRun=false to merge.

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": {
      "projectId": "<projectId>",
      "targetProfileId": "<targetProfileId>",
      "sourceContactId": "<sourceContactId>"
    },
    "name": "merge_contact_profiles"
  }
}

Input Schema

NameRequiredDescriptionDefault
dryRunNoIf true (default), validates without merging. Set to false to actually merge.
projectIdYesThe project ID the profiles belong to
sourceContactIdYesA contact ID whose profile will be merged into the target (see contactIds in get_contact_profile / export_contact_profile)
targetProfileIdYesThe profile ID that will receive the merged data

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.2.1
    • addedInput schema / properties / projectId
      Added value: +{
      +  "description": "The project ID the profiles belong to",
      +  "type": "string"
      +}
    • addedInput schema / properties / sourceContactId
      Added value: +{
      +  "description": "A contact ID whose profile will be merged into the target (see contactIds in get_contact_profile / export_contact_profile)",
      +  "type": "string"
      +}
    • removedInput schema / properties / sourceProfileId
      Removed value: -{
      -  "description": "The source profile ID (will be merged into target)",
      -  "type": "string"
      -}
    • changedInput schema / properties / targetProfileId / description
      Previous value: -"The target profile ID (will receive the merged data)"New value: +"The profile ID that will receive the merged data"
    • changedInput schema / required
      Previous value: -[
      -  "sourceProfileId",
      -  "targetProfileId"
      -]New value: +[
      +  "projectId",
      +  "targetProfileId",
      +  "sourceContactId"
      +]
  2. First observedv0.1.4

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, but the description adds a genuinely non-obvious operational fact: the write only happens when dryRun is explicitly set to false, and it labels the operation MUTATING. It does not discuss reversibility or what happens to the source profile after the merge.

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: purpose first, usage condition second, critical dryRun caveat last. Zero filler and the most action-relevant detail (dryRun=false) is given prominence.

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?

For a four-parameter mutating tool with no output schema, the description covers what it does, when to use it, and the fact that the default is a non-committing validation pass. It stops short of explaining post-merge consequences (fate of the source profile, reversibility), which an agent merging profiles would want.

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 sourceContactId, targetProfileId, and the dryRun default. The description restates the source-to-target direction and the dryRun requirement rather than adding new parameter semantics, so the baseline of 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 (merges), resource (contact profile), and the exact data flow (source contact ID into a target profile, combining data and contact IDs). This is clearly distinguishable from siblings such as unmerge_contact_profiles, update_contact_profile, and remove_contact_id.

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?

Provides a clear triggering condition: 'Use when the same user has multiple profiles.' It does not, however, name the inverse sibling (unmerge_contact_profiles) or state when not to use it, so the routing guidance is good but not exhaustive.

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

Deploy Server

Other Tools