PixelFlow

Delete trigger

delete_trigger

DestructiveIdempotent

Delete a trigger of type url, click, or submit and return the id and type of the removed trigger. Its event stops being sent from that trigger once visitors' browsers pick up the new site configuration. Repeating an idempotency_key deletes once. Use it when the user wants to stop sending an event from that trigger.

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": {
      "site_id": "<site_id>",
      "idempotency_key": "<idempotency_key>",
      "type": "<type>",
      "trigger_id": "<trigger_id>"
    },
    "name": "delete_trigger"
  }
}

Input Schema

Name	Required	Description
`type`	Yes	Type of the stored trigger, as returned by list_triggers.
`site_id`	Yes	Site to act on, as returned by list_sites.
`trigger_id`	Yes	Trigger id as returned by list_triggers or create_trigger.
`idempotency_key`	Yes	Unique string per intended change, such as a UUID. Repeating a key returns the first result instead of writing again.

Output Schema

Name	Required	Description
`type`	Yes	Type of the removed trigger.
`saved`	Yes	Whether the request was applied. Always true on success.
`deleted`	Yes	Whether the trigger was removed. Always true on success.
`trigger_id`	Yes	Id of the removed trigger.

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedNov 2, 2026

changedInput schema / properties / idempotency_key / description

Previous value: -"Key for this approval line. The same key twice creates or changes one trigger"New value: +"Unique string per intended change, such as a UUID. Repeating a key returns the first result instead of writing again."

removedInput schema / properties / kind

Removed value: -{
-  "description": "page, click, or form",
-  "type": "string"
-}

removedInput schema / properties / site

Removed value: -{
-  "description": "Domain, id, or external id from list_sites",
-  "type": "string"
-}

addedInput schema / properties / site_id

Added value: +{
+  "description": "Site to act on, as returned by list_sites.",
+  "type": "integer"
+}

removedInput schema / properties / suggestion_id

Removed value: -{
-  "description": "Proposal id when this line came from suggest_triggers. Omit otherwise",
-  "type": "string"
-}

changedInput schema / properties / trigger_id / description

Previous value: -"trigger_id from list_triggers or from create_trigger"New value: +"Trigger id as returned by list_triggers or create_trigger."

changedInput schema / properties / trigger_id / type
```
Previous value: -"number"New value: +"integer"
```

addedInput schema / properties / type

Added value: +{
+  "description": "Type of the stored trigger, as returned by list_triggers.",
+  "enum": [
+    "url",
+    "click",
+    "submit"
+  ],
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "site",
-  "kind",
-  "trigger_id",
-  "idempotency_key"
-]New value: +[
+  "site_id",
+  "idempotency_key",
+  "type",
+  "trigger_id"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "deleted": {
+      "description": "Whether the trigger was removed. Always true on success.",
+      "type": "boolean"
+    },
+    "saved": {
+      "description": "Whether the request was applied. Always true on success.",
+      "type": "boolean"
+    },
+    "trigger_id": {
+      "description": "Id of the removed trigger.",
+      "type": "integer"
+    },
+    "type": {
+      "description": "Type of the removed trigger.",
+      "enum": [
+        "url",
+        "click",
+        "submit"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "saved",
+    "deleted",
+    "trigger_id",
+    "type"
+  ],
+  "type": "object"
+}

First observedOct 23, 2026

TDQS

A4.2/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, so the safety profile is covered. The description adds genuinely new context: the event stops being sent only after visitors' browsers pick up the new site configuration (propagation delay), and that repeating an idempotency_key deletes only once. It does not discuss permissions or irreversibility beyond the destructive hint.

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 tight sentences, front-loaded with the action and return value, then behavior, then usage. The idempotency sentence duplicates the schema's own wording, which is the only wasted space.

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?

An output schema exists, so return values need not be explained, and annotations cover the destructive/idempotent profile. The description still adds the propagation-delay nuance an agent needs to set user expectations, leaving nothing material missing.

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 all four parameters are already documented, including the idempotency_key repeat behavior. The description's mention of the type enum and idempotency semantics largely restates the schema, 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 and resource ('Delete a trigger'), constrains it to the three trigger types, and describes the return value (id and type of the removed trigger). An agent can distinguish this from create_trigger/update_trigger 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 Guidelines4/5

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

Explicitly says 'Use it when the user wants to stop sending an event from that trigger,' which gives a clear selection condition. It does not name alternatives (e.g., update_trigger to modify rather than remove) or state when not to use it, so it falls short of a 5.

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

All PixelFlow 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.