AgentPixel

Read contacts

get_contacts

Read-onlyIdempotent

Contacts for one pixel.

    Pass on as a UTC day, or after as the high_water from the previous pull. Use high_water as the next cursor.
    New contacts can arrive between reads. This does not identify new visitors.
    Evaluation returns labeled synthetic examples only after current resolution consent is saved; withdrawal hides them.

Input Schema

TableJSON Schema

Name	Required	Description
`on`	No	UTC calendar date in YYYY-MM-DD form. Returns contacts stored on that day. Use exactly one of on or after. Example: 2026-10-12
`after`	No	Cursor for incremental reads: the high_water value from your previous pull, or 0 to start at the first stored contact. Use exactly one of on or after. Example: 0
`pixel_id`	Yes	pixel_id whose contacts to read. Example: px_7a1b2c3d4e5f6a7b

Output Schema

TableJSON Schema

Name	Required	Description	Default
`on`	No
`after`	No
`contacts`	Yes
`pixel_id`	Yes
`data_kind`	No
`high_water`	No
`evaluation_mode`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 10, 2026

addedInput schema / properties / after / description

Added value: +"Cursor for incremental reads: the high_water value from your previous pull, or 0 to start at the first stored contact. Use exactly one of on or after. Example: 0"

addedInput schema / properties / on / description

Added value: +"UTC calendar date in YYYY-MM-DD form. Returns contacts stored on that day. Use exactly one of on or after. Example: 2026-10-12"

changedInput schema / properties / pixel_id / description

Previous value: -"Exact pixel_id returned by create_pixel or list_pixels; never an account ID"New value: +"pixel_id whose contacts to read. Example: px_7a1b2c3d4e5f6a7b"

Changed9 schema fields changedOct 9, 2026

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

addedInput schema / oneOf

Added value: +[
+  {
+    "properties": {
+      "after": {
+        "type": "null"
+      },
+      "on": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "on"
+    ]
+  },
+  {
+    "properties": {
+      "after": {
+        "type": "integer"
+      },
+      "on": {
+        "type": "null"
+      }
+    },
+    "required": [
+      "after"
+    ]
+  }
+]

changedInput schema / properties / after / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "Stored contact ID high_water from previous pull; 0 starts at first contact. Choose after OR on, exactly one",
+    "maximum": 9223372036854776000,
+    "minimum": 0,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / on / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "UTC calendar date YYYY-MM-DD; choose on OR after, exactly one",
+    "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / pixel_id / description

Added value: +"Exact pixel_id returned by create_pixel or list_pixels; never an account ID"

addedInput schema / properties / pixel_id / maxLength
```
Added value: +80
```
addedInput schema / properties / pixel_id / minLength
```
Added value: +1
```
addedInput schema / properties / pixel_id / pattern
```
Added value: +"^[A-Za-z0-9_-]+$"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "Contact": {
+      "additionalProperties": true,
+      "properties": {
+        "contact": {
+          "additionalProperties": true,
+          "title": "Contact",
+          "type": "object"
+        },
+        "hem": {
+          "title": "Hem",
+          "type": "string"
+        },
+        "id": {
+          "title": "Id",
+          "type": "integer"
+        },
+        "resolved_at": {
+          "title": "Resolved At",
+          "type": "string"
+        },
+        "synthetic": {
+          "anyOf": [
+            {
+              "type": "boolean"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Synthetic"
+        }
+      },
+      "required": [
+        "id",
+        "hem",
+        "resolved_at",
+        "contact"
+      ],
+      "title": "Contact",
+      "type": "object"
+    }
+  },
+  "additionalProperties": true,
+  "properties": {
+    "after": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "After"
+    },
+    "contacts": {
+      "items": {
+        "$ref": "#/$defs/Contact"
+      },
+      "title": "Contacts",
+      "type": "array"
+    },
+    "data_kind": {
+      "anyOf": [
+        {
+          "enum": [
+            "synthetic",
+            "resolved"
+          ],
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Data Kind"
+    },
+    "evaluation_mode": {
+      "anyOf": [
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Evaluation Mode"
+    },
+    "high_water": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "High Water"
+    },
+    "on": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "On"
+    },
+    "pixel_id": {
+      "title": "Pixel Id",
+      "type": "string"
+    }
+  },
+  "required": [
+    "pixel_id",
+    "contacts"
+  ],
+  "title": "Contacts",
+  "type": "object"
+}

First observedOct 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, so the description earns credit for going further: new contacts can arrive between reads (no stable snapshot), results are scoped to a single pixel, and evaluation data is consent-gated (synthetic examples only after consent is saved, hidden on withdrawal). It omits rate limits or page-size behavior, keeping it at a strong 4 rather than 5.

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?

Short and front-loaded with the one-line purpose, and every sentence carries information. The phrasing is uneven ('Pass on as a UTC day' reads ambiguously) and the consent sentence is somewhat cryptic, but there is no filler.

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?

With an output schema handling return values, 100% schema coverage, and annotations covering safety, the description supplies what remains: pagination mechanics, eventual-consistency caveat, and consent-gated visibility. Only sibling differentiation is unaddressed, which is a minor gap given the unique resource.

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%, and the schema already documents 'exactly one of on or after', the YYYY-MM-DD format, and that 'after' is the previous high_water. The description mostly restates this, adding only light framing about the cursor round-trip. Baseline 3 applies when the schema carries the parameter burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the resource and scope precisely: 'Contacts for one pixel.' The read action is implied by the name/annotations, and 'contacts' is a distinct resource from siblings like get_pixel/list_pixels. It stops short of naming any sibling or explicitly contrasting alternatives, so not a 5.

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?

Gives concrete operating instructions: pass 'on' as a UTC day, or 'after' as the high_water from the previous pull, and use high_water as the next cursor. This tells the agent how to drive the tool across reads, but names no alternatives and gives no when-not guidance (e.g. which mode to prefer for which workflow).

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.