AgentPixel

Create site pixel

create_pixel

Create a pixel for a domain.

    Does not create an API key. The account must already be active.
    Next: call configure_consent(pixel_id, controller_name, purposes) and install the snippet it returns.
    Do not install a snippet before consent is configured. install_status starts as not_checked until check_install runs.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`domain`	Yes	Public hostname of the site, without scheme, port, path or IP address. Example: shop.example.com

Output Schema

TableJSON Schema

Name	Required	Description	Default
`domain`	Yes
`snippet`	No
`pixel_id`	Yes
`data_kind`	Yes
`checked_at`	No
`check_error`	No
`install_status`	Yes
`consent_enabled`	No
`evaluation_mode`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 10, 2026

changedInput schema / properties / domain / description

Previous value: -"Public hostname only, without scheme, port, path, or IP address. Evaluator: staging.allsourcedata.io only"New value: +"Public hostname of the site, without scheme, port, path or IP address. Example: shop.example.com"

Changed6 schema fields changedOct 9, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / domain / description

Added value: +"Public hostname only, without scheme, port, path, or IP address. Evaluator: staging.allsourcedata.io only"

addedInput schema / properties / domain / maxLength
```
Added value: +253
```
addedInput schema / properties / domain / minLength
```
Added value: +3
```

addedInput schema / properties / domain / pattern

Added value: +"^[A-Za-z0-9](?:[A-Za-z0-9.-]*[A-Za-z0-9])?$"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "check_error": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Check Error"
+    },
+    "checked_at": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Checked At"
+    },
+    "consent_enabled": {
+      "anyOf": [
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Consent Enabled"
+    },
+    "data_kind": {
+      "enum": [
+        "synthetic",
+        "resolved"
+      ],
+      "title": "Data Kind",
+      "type": "string"
+    },
+    "domain": {
+      "title": "Domain",
+      "type": "string"
+    },
+    "evaluation_mode": {
+      "title": "Evaluation Mode",
+      "type": "boolean"
+    },
+    "install_status": {
+      "enum": [
+        "not_checked",
+        "installed",
+        "not_installed",
+        "unreachable"
+      ],
+      "title": "Install Status",
+      "type": "string"
+    },
+    "pixel_id": {
+      "title": "Pixel Id",
+      "type": "string"
+    },
+    "snippet": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Snippet"
+    }
+  },
+  "required": [
+    "pixel_id",
+    "domain",
+    "install_status",
+    "evaluation_mode",
+    "data_kind"
+  ],
+  "title": "Pixel",
+  "type": "object"
+}

First observedOct 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, so the bar is lower. The description still adds real value: it clarifies the API-key side effect does not occur, states the account prerequisite, and describes the install_status lifecycle starting at 'not_checked'. It does not say what happens on a duplicate domain, which is the one notable gap.

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?

Front-loaded one-line purpose followed by terse, distinct operational notes; no filler, and each line carries a rule the agent must obey (no API key, active account, consent before install, initial status).

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-value details are unnecessary. For a mutating tool with only one required parameter, the description covers preconditions, sequencing, and state initialization, which is everything needed to invoke it correctly.

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?

Only one parameter and schema description coverage is 100% — the schema already specifies the hostname format, pattern, length bounds, and an example. The description adds nothing about the domain argument beyond reassembling 'for a domain', so the baseline of 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 precise verb+resource ('Create a pixel for a domain') and explicitly excludes a confusing near-neighbor by noting it 'Does not create an API key', which separates it from the create_api_key sibling. An agent can identify this as the pixel-provisioning tool 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?

Gives a hard precondition ('The account must already be active'), a required follow-up ('Next: call configure_consent...'), and an explicit ordering prohibition ('Do not install a snippet before consent is configured'). This tells the agent both when to call it and what must happen before/after, including the initial 'not_checked' state.

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

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