Skip to main content
Glama
TsvetanG2

cognigy-ai-mcp-management-server

by TsvetanG2
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript

update_analytics_record

Idempotent

Updates Cognigy.AI session analytics records to add custom tracking properties to conversation analytics. Set dryRun=false to apply changes.

Instructions

Updates Cognigy.AI analytics records for a session. Use this to add custom tracking properties to conversation analytics. MUTATING: Set dryRun=false to update.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dryRunNoIf true (default), validates without updating. Set to false to actually update.
inputIdNoRestrict the update to a single input (message) of the session
contactIdYesThe contact (user) ID of the conversation
projectIdYesThe project ID
sessionIdYesThe session ID to update analytics for
propertiesYesAnalytics fields to set. Editable fields include rating, ratingComment, custom1..custom10, intent, intentScore, slots, state, mode, flowName, localeName, inHandoverRequest, inHandoverConversation, handoverEscalations

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.1
    • addedInput schema / properties / contactId
      Added value: +{
+  "description": "The contact (user) ID of the conversation",
+  "type": "string"
+}
    • addedInput schema / properties / inputId
      Added value: +{
+  "description": "Restrict the update to a single input (message) of the session",
+  "type": "string"
+}
    • changedInput schema / properties / properties / description
      Previous value: -"Custom analytics properties to set"New value: +"Analytics fields to set. Editable fields include rating, ratingComment, custom1..custom10, intent, intentScore, slots, state, mode, flowName, localeName, inHandoverRequest, inHandoverConversation, handoverEscalations"
    • changedInput schema / required
      Previous value: -[
-  "projectId",
-  "sessionId",
-  "properties"
-]New value: +[
+  "projectId",
+  "contactId",
+  "sessionId",
+  "properties"
+]
  2. First observedv0.1.4

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), so the bar is lower. The description usefully reinforces this with 'MUTATING: Set dryRun=false to update,' flagging the non-obvious safe-by-default dry-run behavior, but adds nothing about permissions or what happens to unlisted fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with purpose followed by use case and the mutation caveat. Well sized with no filler, though the 'MUTATING:' fragment is slightly tacked on in style.

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 mutation tool with a dry-run default and no output schema, the description covers purpose, primary use, and the safety-critical dryRun flag. Nothing essential is missing, though a note on idempotency/field-merge behavior would round it out.

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 every parameter is already documented, and the description only loosely gestures at the properties field via 'custom tracking properties.' Baseline 3 is appropriate since the schema carries the semantic load.

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?

States a specific verb and resource ('Updates Cognigy.AI analytics records for a session') and names the affected entity (session). It is clearly distinguishable from read-only analytics siblings like get_conversation_metrics, though it does not explicitly name those siblings.

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?

'Use this to add custom tracking properties to conversation analytics' gives a use case but no when-not conditions or named alternatives. Usage is implied rather than contrasted against the other analytics/metrics tools in the sibling set.

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