OneLence

Record a change

onelence_record_change

Idempotent

Records a change the team made outside OneLence (budget, offer, pricing, tracking, creative, campaign, partner, email, social post, launch, or offline activity such as a TV or radio ad, billboard, influencer campaign, press coverage or event), on one source or the whole site, so OneLence can observe the period after it. Offline activity is recorded on the whole site only. Optional ends_on, image_url, link_url and markets are stored with the change when they are sent. It changes nothing on ad platforms. The preview needs label, occurred_on, timezone. 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_record_change"
  }
}

Input Schema

Name	Required	Description
`note`	No
`site`	No	Site domain (e.g. example.com) or site id. Defaults to the workspace's newest active site.
`time`	No	Local time (HH:MM). Default 12:00.
`label`	No	What changed, in a few words, e.g. "Raised the TikTok budget".
`family`	No
`ends_on`	No	Last local date the change ran through (YYYY-MM-DD), from the start date through 730 days after it.
`markets`	No	One to 30 different two-letter country codes, such as IT or DE.
`link_url`	No	https address for the change, at most 2048 characters, without a username or password.
`timezone`	No	IANA time zone, e.g. Europe/Rome.
`image_url`	No	https address of a picture, at most 2048 characters, without a username or password.
`source_id`	No	The source it was made on (from the sources list). Without it, the whole site.
`occurred_on`	No	Local date of the change (YYYY-MM-DD).
`confirmation_id`	No	Only when applying: the confirmation_id from the preview, after the user agreed.
`quantified_change`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 9, 2026

addedInput schema / properties / ends_on

Added value: +{
+  "description": "Last local date the change ran through (YYYY-MM-DD), from the start date through 730 days after it.",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}

changedInput schema / properties / family / enum

Previous value: -[
-  "budget_change",
-  "offer_change",
-  "pricing_change",
-  "tracking_change",
-  "creative_change",
-  "campaign_change",
-  "partner_change",
-  "other"
-]New value: +[
+  "budget_change",
+  "campaign_change",
+  "creative_change",
+  "partner_change",
+  "email_campaign",
+  "social_post",
+  "pricing_change",
+  "offer_change",
+  "tracking_change",
+  "site_launch",
+  "tv_radio_ad",
+  "outdoor_ad",
+  "influencer_campaign",
+  "press_coverage",
+  "event_sponsorship",
+  "other"
+]

addedInput schema / properties / image_url

Added value: +{
+  "description": "https address of a picture, at most 2048 characters, without a username or password.",
+  "maxLength": 2048,
+  "type": "string"
+}

addedInput schema / properties / link_url

Added value: +{
+  "description": "https address for the change, at most 2048 characters, without a username or password.",
+  "maxLength": 2048,
+  "type": "string"
+}

addedInput schema / properties / markets

Added value: +{
+  "description": "One to 30 different two-letter country codes, such as IT or DE.",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 30,
+  "type": "array"
+}

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": {
+                "family": {
+                  "anyOf": [
+                    {
+                      "type": "string"
+                    },
+                    {
+                      "type": "null"
+                    }
+                  ]
+                },
+                "id": {
+                  "anyOf": [
+                    {
+                      "type": "string"
+                    },
+                    {
+                      "type": "null"
+                    }
+                  ]
+                },
+                "label": {
+                  "type": "string"
+                },
+                "note": {
+                  "type": "string"
+                },
+                "object": {
+                  "const": "recorded_change_receipt",
+                  "type": "string"
+                },
+                "occurred_at": {
+                  "type": "string"
+                },
+                "quantified_change": {
+                  "anyOf": [
+                    {
+                      "type": "string"
+                    },
+                    {
+                      "type": "null"
+                    }
+                  ]
+                },
+                "status": {
+                  "enum": [
+                    "created",
+                    "existing"
+                  ],
+                  "type": "string"
+                },
+                "target": {
+                  "properties": {
+                    "kind": {
+                      "enum": [
+                        "source",
+                        "source_family",
+                        "source_set",
+                        "portfolio"
+                      ],
+                      "type": "string"
+                    },
+                    "label": {
+                      "type": "string"
+                    }
+                  },
+                  "required": [
+                    "kind",
+                    "label"
+                  ],
+                  "type": "object"
+                },
+                "timezone": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "object",
+                "id",
+                "status",
+                "label",
+                "occurred_at",
+                "timezone",
+                "target",
+                "family",
+                "quantified_change",
+                "note"
+              ],
+              "type": "object"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "status": {
+          "const": "applied",
+          "type": "string"
+        }
+      },
+      "required": [
+        "object",
+        "status",
+        "result"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}

First observedOct 4, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations only say this is non-destructive, non-idempotent-breaking, closed-world write; the description adds real behavior the agent cannot get elsewhere: a mandatory preview/confirm handshake, the fact that nothing is pushed to ad platforms, that optional fields are persisted with the change when sent, and the whole-site restriction for offline activity. It also reveals the preview's required fields (label, occurred_on, timezone), which the schema's empty required array does not.

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?

Purpose is front-loaded, the scope constraint follows, and the two-step workflow closes it out in a sensible order. The one blemish is the 12-item run-on parenthetical in the opening sentence, which could be tightened, though it does double duty by hinting at family values.

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 14-parameter tool with a nested object and a preview/apply cycle, the description covers the workflow, scope and optionality well, and an output schema exists so return values need no explanation. The notable omission is quantified_change: its metric/unit/change/before/after semantics are never mentioned in either description or nested schema descriptions, leaving the agent to infer how to express a measurable change.

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 79%, so the schema does most of the work, but the description adds two things it cannot: which fields are mandatory for a successful preview, and which fields (ends_on, image_url, link_url, markets) are stored only conditionally. The prose change-type list also implicitly maps onto the undocumented 16-value family enum. It says nothing about quantified_change, the nested object, which is the largest remaining gap.

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?

"Records a change the team made outside OneLence" states a specific verb plus resource, and the parenthetical enumerates the change types (budget, offer, pricing, tracking, creative, campaign...). It also fixes the scope ("on one source or the whole site"), so an agent can distinguish it from the read-side onelence_list_changes and from onelence_save_campaign_context.

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?

It gives an explicit two-step protocol: call with the change to get a summary and confirmation_id, show the user, then call again with just confirmation_id. It also bounds usage ("Offline activity is recorded on the whole site only") and negates a wrong expectation ("It changes nothing on ad platforms"). What's missing is any pointer to siblings such as onelence_list_changes for checking what was already recorded, so it stops short of full alternative routing.

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.