Mark

Delete Strategy Item

delete_strategy_item

Destructive

Permanently deletes a persona, pillar, angle, market or KPI target, or deletes a buyer question. A deleted buyer question leaves every list and future AI answer checks, but its past answers and wrong answers stay, and saving the same text again with save_strategy_item brings it back. To pause a question instead, call save_strategy_item with active: false. Other deletes cannot be undone. An item still in use is refused: a persona or pillar that angles use (the error names them, so delete or move those angles first), anything posts use, or a market that answer-engine checks or monthly AI-visibility results use. To retire an item that is in use, call save_strategy_item with its id and active: false. Related: save_strategy_item, get_brand_context.

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": {
      "kind": "<kind>",
      "id": "<id>"
    },
    "name": "delete_strategy_item"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	The item id from get_brand_context.
`kind`	Yes	Kind to delete.

Output Schema

Name	Required	Description	Default
`id`	Yes
`kind`	Yes
`appUrl`	Yes
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 3, 2026

changedInput schema / properties / kind / description

Previous value: -"Kind to delete. Buyer questions cannot be deleted."New value: +"Kind to delete."

changedInput schema / properties / kind / enum

Previous value: -[
-  "persona",
-  "pillar",
-  "angle",
-  "market",
-  "kpi_target"
-]New value: +[
+  "persona",
+  "pillar",
+  "angle",
+  "market",
+  "kpi_target",
+  "buyer_question"
+]

Changed2 schema fields changedOct 8, 2026

addedOutput schema / properties / appUrl
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "id",
-  "kind",
-  "result"
-]New value: +[
+  "appUrl",
+  "id",
+  "kind",
+  "result"
+]

First observedOct 1, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds real substance beyond that: the asymmetry between buyer questions (removed from lists, past answers retained, resurrectable by re-saving) and other kinds (irreversible), plus the in-use refusal with an error that names blocking angles. It stops short of describing permissions or response payload, but with the output schema present and safety annotations covering the basics, this is strong added context.

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?

Front-loaded with the most consequential distinction (buyer question vs. everything else) before the precondition rules. The save_strategy_item with active:false remedy appears twice for two different scenarios, which is slightly repetitive but each occurrence answers a distinct question, so the repetition is defensible.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter destructive tool, the description covers destructiveness, exceptions, alternatives, and related tools, and an output schema exists so return values need no explanation. Nothing an agent needs in order to call this safely is missing.

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 100%, so baseline is 3, but the description adds meaning the enum alone does not: the semantics of deletion vary by kind, with buyer_question being a soft removal and the other five being permanent and blocked when still referenced. The id parameter is only tied back to get_brand_context, which the schema already states, so it is not a 5.

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?

Opening sentence names a specific verb (permanently deletes) and enumerates the exact resources (persona, pillar, angle, market, KPI target, buyer question), and immediately flags that buyer questions behave differently. An agent can distinguish this from siblings like delete_post or delete_assets without opening any 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?

It gives explicit alternate paths: use save_strategy_item with active:false to pause a question, and the same call with an id to retire an item that is in use. It also states the preconditions for a successful delete and what to do when the refusal happens, leaving nothing to inference.

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

All Mark 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?