XCut AI – Viral Content Research

Update a brand memory fact

xcut_update_memory

DestructiveIdempotent

Use this when the user asks to change a saved brand memory fact. Replaces that fact's text and category (the old text is not kept). Needs the fact's id from xcut_get_brand. Free. Do not use to add a new fact (use xcut_save_memory).

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": {
      "canvas_id": "<canvas_id>",
      "memory_id": "<memory_id>",
      "text": "<text>"
    },
    "name": "xcut_update_memory"
  }
}

Input Schema

Name	Required	Description
`text`	Yes	The fact's new text.
`category`	No	New kind of fact. Omit to keep the current one.
`canvas_id`	Yes	Canvas id (a UUID) from xcut_list_canvases.
`memory_id`	Yes	Id of the fact to change, from xcut_get_brand.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 10, 2026

addedInput schema / properties / category / anyOf

Added value: +[
+  {
+    "enum": [
+      "subject_type",
+      "brand_name",
+      "niche",
+      "brand_voice",
+      "language",
+      "visual_style",
+      "audience",
+      "content_format",
+      "content_pillars",
+      "hook_patterns",
+      "cta_style",
+      "kpi_focus",
+      "platform",
+      "posting_schedule",
+      "offer",
+      "competitors",
+      "constraint",
+      "content_preference",
+      "fact",
+      "other"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / category / default
```
Previous value: -"fact"New value: +null
```

changedInput schema / properties / category / description

Previous value: -"What kind of fact it is."New value: +"New kind of fact. Omit to keep the current one."

removedInput schema / properties / category / enum

Removed value: -[
-  "subject_type",
-  "brand_name",
-  "niche",
-  "brand_voice",
-  "language",
-  "visual_style",
-  "audience",
-  "content_format",
-  "content_pillars",
-  "hook_patterns",
-  "cta_style",
-  "kpi_focus",
-  "platform",
-  "posting_schedule",
-  "offer",
-  "competitors",
-  "constraint",
-  "content_preference",
-  "fact",
-  "other"
-]

removedInput schema / properties / category / type
```
Removed value: -"string"
```

First observedOct 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds what the annotations cannot: the old text is discarded rather than versioned, the fact must be resolved first via xcut_get_brand, and the call is free. It stops short of describing the response or any side effects on dependent content that referenced the fact.

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?

Four short sentences, front-loaded with the trigger and followed by the destructive effect, prerequisite, cost and exclusion in descending order of importance. Slight redundancy between 'Replaces that fact's text and category' and the parenthetical '(the old text is not kept)'.

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, annotation-backed mutation tool with no output schema, the definition covers trigger, exclusion, alternative, prerequisite and irreversibility. What remains unstated is the return payload and whether callers of the fact elsewhere are affected.

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 already documents text, category (with the full enum and 'omit to keep current'), canvas_id and memory_id including their source tools. The description adds no syntax or constraint detail beyond that, so the baseline 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+resource (update a saved brand memory fact) and explicitly contrasts itself with the two nearest siblings: not xcut_save_memory (add) and implicitly not xcut_delete_memory. An agent can route between the three memory tools without opening a schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('when the user asks to change a saved brand memory fact'), an explicit exclusion ('Do not use to add a new fact'), and names the alternative tool that handles the excluded case. Prerequisite chain (id from xcut_get_brand) is also stated.

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

All XCut AI – Viral Content Research 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.

Resources

Need Help?