OneLence

Rename a conversion event

onelence_update_event_definition

DestructiveIdempotent

Changes a conversion event's display name or the event name the SDK sends. The new name replaces the old one, which is not kept. The preview needs event_definition_id. Two steps: call with the change to get a summary and a confirmation_id, show the summary to the user, and only after they agree call again with just confirmation_id.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "onelence_update_event_definition"
  }
}

Input Schema

Name	Required	Description
`name`	No
`event_name`	No
`confirmation_id`	No	Only when applying: the confirmation_id from the preview, after the user agreed.
`event_definition_id`	No	id from the event definitions list.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "oneOf": [
+    {
+      "properties": {
+        "confirmation_id": {
+          "type": "string"
+        },
+        "expires_at": {
+          "type": "string"
+        },
+        "next_step": {
+          "type": "string"
+        },
+        "object": {
+          "const": "write_preview",
+          "type": "string"
+        },
+        "status": {
+          "const": "confirmation_required",
+          "type": "string"
+        },
+        "summary": {
+          "properties": {
+            "details": {
+              "items": {
+                "type": "string"
+              },
+              "type": "array"
+            },
+            "title": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "title",
+            "details"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "object",
+        "status",
+        "confirmation_id",
+        "expires_at",
+        "summary",
+        "next_step"
+      ],
+      "type": "object"
+    },
+    {
+      "properties": {
+        "object": {
+          "const": "write_result",
+          "type": "string"
+        },
+        "result": {
+          "anyOf": [
+            {
+              "properties": {
+                "created_at": {
+                  "anyOf": [
+                    {
+                      "type": "string"
+                    },
+                    {
+                      "type": "null"
+                    }
+                  ]
+                },
+                "event_name": {
+                  "type": "string"
+                },
+                "id": {
+                  "type": "string"
+                },
+                "kind": {
+                  "anyOf": [
+                    {
+                      "type": "string"
+                    },
+                    {
+                      "type": "null"
+                    }
+                  ]
+                },
+                "name": {
+                  "type": "string"
+                },
+                "object": {
+                  "const": "event_definition",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "object",
+                "id",
+                "name",
+                "event_name",
+                "kind",
+                "created_at"
+              ],
+              "type": "object"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "status": {
+          "const": "applied",
+          "type": "string"
+        }
+      },
+      "required": [
+        "object",
+        "status",
+        "result"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}

First observedOct 4, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Goes well beyond the annotations: the annotations only say destructiveHint=true and idempotentHint=true, while the description explains exactly what is destroyed (the old name is not kept) and the human-in-the-loop preview/confirm protocol that guards the mutation. That is the kind of operational context an agent cannot infer from structured 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, front-loaded sentences that lead with the effect, then the irreversibility, then the workflow. The sentence 'The preview needs event_definition_id' is terse to the point of being slightly cryptic, but there is no filler.

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?

A destructive mutation tool with an output schema, and the description covers the risk profile, the required identifier, and the two-phase invocation, so return-value details are rightly omitted. The one residual gap is that it never states whether passing both name and event_name in one call is allowed or how to preview clearing a field.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%, and the description compensates by mapping the two name fields to distinct meanings (display name vs. the event name sent by the SDK) and by tying event_definition_id to the preview step and confirmation_id to the apply step. It stops short of an explicit field-by-field mapping, so an agent must infer which of name/event_name is the display name.

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: changes a conversion event's display name or the event name the SDK sends. This is materially different from creating (save_event_definition) or deleting an event definition, though the description never names those siblings explicitly.

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?

Gives explicit sequencing: call with the change to get a preview summary plus confirmation_id, show it to the user, then call again with only confirmation_id once they agree. It does not, however, contrast this tool with save_event_definition or explain what to do when the user declines.

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

All OneLence tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.