PixelFlow

Update pixel

update_pixel

DestructiveIdempotent

Change the label or the test event code of a connected ad platform pixel. Returns the pixel's label and test event code after the change. A test event code sends events to the ad platform's test events view, for debugging. An empty test event code turns test mode off. Test mode also turns off by itself at test_mode_ends_at. Fields left out stay unchanged. The pixel id and access token can only be changed in the dashboard. Use it when the user wants to rename a pixel or check events in the ad platform's test view.

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>",
      "pixel_id": "<pixel_id>"
    },
    "name": "update_pixel"
  }
}

Input Schema

Name	Required	Description
`label`	No	Display name for the pixel.
`site_id`	Yes	Site to act on, as returned by list_sites.
`pixel_id`	Yes	Pixel id as returned by get_site_status (`pixels[].pixel_id`).
`test_event_code`	No	Test event code from the ad platform's events manager, such as TEST12345. Empty string clears it.

Output Schema

Name	Required	Description
`label`	Yes	Pixel label after the change.
`pixel_id`	Yes	Pixel id.
`test_event_code`	Yes	Test event code after the change. null: test mode is off.
`test_mode_ends_at`	Yes	When test mode turns off by itself and the test event code is cleared. A new code sent while test mode is on keeps this time. null: test mode is off.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 2, 2026
- addedOutput schema / properties / test_event_code / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / test_event_code / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / test_mode_ends_at / anyOf
```
Added value: +[
+  {
+    "format": "date-time",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / test_mode_ends_at / format
```
Removed value: -"date-time"
```
- removedOutput schema / properties / test_mode_ends_at / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

Changed10 schema fields changedNov 2, 2026

changedInput schema / properties / label / description

Previous value: -"Name shown for this Pixel"New value: +"Display name for the pixel."

addedInput schema / properties / label / maxLength
```
Added value: +255
```

changedInput schema / properties / pixel_id / description

Previous value: -"Pixel id from get_site_status"New value: +"Pixel id as returned by get_site_status (`pixels[].pixel_id`)."

changedInput schema / properties / pixel_id / type

Previous value: -"number"New value: +"integer"

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"
+}

changedInput schema / properties / test_event_code / description

Previous value: -"Meta test event code. An empty string clears test mode"New value: +"Test event code from the ad platform's events manager, such as TEST12345. Empty string clears it."

addedInput schema / properties / test_event_code / maxLength
```
Added value: +255
```

changedInput schema / required

Previous value: -[
-  "site",
-  "pixel_id"
-]New value: +[
+  "site_id",
+  "pixel_id"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "label": {
+      "description": "Pixel label after the change.",
+      "type": "string"
+    },
+    "pixel_id": {
+      "description": "Pixel id.",
+      "type": "integer"
+    },
+    "test_event_code": {
+      "description": "Test event code after the change. null: test mode is off.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "test_mode_ends_at": {
+      "description": "When test mode turns off by itself and the test event code is cleared. A new code sent while test mode is on keeps this time. null: test mode is off.",
+      "format": "date-time",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "pixel_id",
+    "label",
+    "test_event_code",
+    "test_mode_ends_at"
+  ],
+  "type": "object"
+}

First observedOct 23, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=true), the description explains test event code semantics, that an empty value turns test mode off, that test mode auto-expires at test_mode_ends_at, and that omitted fields remain unchanged. These are concrete behavioral traits an agent needs before mutating a pixel.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core action, then adds only necessary behavioral details. Every sentence earns its place by clarifying scope, test-mode behavior, omitted-field behavior, or intended use.

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 in detail, and the input schema fully documents all four parameters. The description completes the picture with mutation semantics, field omission behavior, and constraints on what cannot be changed.

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 description coverage is 100%, so the baseline is 3, but the description adds meaning for test_event_code (empty string clears it and turns test mode off) and for omitted fields (they stay unchanged). The label parameter is left to the schema, but the extra semantics justify a 4.

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?

The description names the specific resource (connected ad platform pixel) and the exact mutable fields (label, test event code), and explicitly excludes pixel id and access token changes. This clearly distinguishes it from broader sibling tools like update_site or update_integration.

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 states concrete when-to-use cases: renaming a pixel or checking events in the ad platform's test view. It also says where the pixel id and access token can be changed, giving a clear boundary, though it does not explicitly name competing sibling tools as alternatives.

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.