AgentPixel

Confirm signup email

confirm_signup

Idempotent

Confirm the email with the 6-digit code, or check whether the email link was clicked.

    Preferred: confirm_signup(account_id, code, signup_token). The first confirmation returns api_key; store it, it is shown once.
    Link clicked instead: call confirm_signup(account_id, signup_token) every 5 seconds, up to 10 minutes, until email_verified is true, then call create_api_key.
    A code allows 5 attempts and lasts 24 hours. For a new code, call resend_code(email).

Input Schema

TableJSON Schema

Name	Required	Description
`code`	No	The 6-digit code from the AgentPixel email. Ask the person to read it to you. Example: 482913
`account_id`	No	account_id returned by signup_free. Use with code, or with signup_token alone to check whether the email link was clicked. Example: 3f1c2b9e-1d2a-4c5b-9e8f-0a1b2c3d4e5f
`signup_token`	No	signup_token returned by signup_free. With code, the first confirmation also returns the API key. Alone with account_id, returns whether the email is confirmed.
`verification_token`	No	Older method: the token value from the confirmation link URL (?token=...). Prefer account_id and code.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`message`	Yes
`confirmed`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedOct 10, 2026

addedInput schema / properties / account_id

Added value: +{
+  "anyOf": [
+    {
+      "description": "account_id returned by signup, not a pixel ID",
+      "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "account_id returned by signup_free. Use with code, or with signup_token alone to check whether the email link was clicked. Example: 3f1c2b9e-1d2a-4c5b-9e8f-0a1b2c3d4e5f",
+  "title": "Account Id"
+}

addedInput schema / properties / code

Added value: +{
+  "anyOf": [
+    {
+      "pattern": "^\\d{6}$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "The 6-digit code from the AgentPixel email. Ask the person to read it to you. Example: 482913",
+  "title": "Code"
+}

addedInput schema / properties / signup_token

Added value: +{
+  "anyOf": [
+    {
+      "description": "Private token returned by signup or confirmation link; never publish it",
+      "maxLength": 512,
+      "minLength": 1,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "signup_token returned by signup_free. With code, the first confirmation also returns the API key. Alone with account_id, returns whether the email is confirmed.",
+  "title": "Signup Token"
+}

addedInput schema / properties / verification_token / anyOf

Added value: +[
+  {
+    "description": "Private token returned by signup or confirmation link; never publish it",
+    "maxLength": 512,
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / verification_token / default
```
Added value: +null
```

changedInput schema / properties / verification_token / description

Previous value: -"Private token returned by signup or confirmation link; never publish it"New value: +"Older method: the token value from the confirmation link URL (?token=...). Prefer account_id and code."

removedInput schema / properties / verification_token / maxLength
```
Removed value: -512
```
removedInput schema / properties / verification_token / minLength
```
Removed value: -1
```
removedInput schema / properties / verification_token / type
```
Removed value: -"string"
```

removedInput schema / required

Removed value: -[
-  "verification_token"
-]

Changed5 schema fields changedOct 9, 2026

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

addedInput schema / properties / verification_token / description

Added value: +"Private token returned by signup or confirmation link; never publish it"

addedInput schema / properties / verification_token / maxLength
```
Added value: +512
```
addedInput schema / properties / verification_token / minLength
```
Added value: +1
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "confirmed": {
+      "title": "Confirmed",
+      "type": "boolean"
+    },
+    "message": {
+      "title": "Message",
+      "type": "string"
+    }
+  },
+  "required": [
+    "confirmed",
+    "message"
+  ],
+  "title": "Confirmed",
+  "type": "object"
+}

First observedOct 9, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations, the description discloses high-value behavior: the first successful confirmation returns an api_key that is shown only once and must be stored, the code allows 5 attempts and expires in 24 hours, and the link-polling loop should run at 5-second intervals for up to 10 minutes. These are non-obvious operational and one-time-secret details.

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 purpose sentence, then two labeled branches ('Preferred' / 'Link clicked') with no filler. Every remaining sentence carries a distinct operational fact (attempt limit, code lifetime, resend escalation).

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 details needn't be restated, yet the description still explains what the agent must do with the returned secret and the success flag. Combined with the alternative-tool routing, nothing needed to call this correctly 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 description coverage is 100%, so the baseline is 3, but the description adds the valid parameter combinations (account_id+code+signup_token for confirmation, account_id+signup_token alone for status checks) that the optional-parameter schema does not express. It does not mention the legacy verification_token path, which only the schema covers.

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 opening sentence states a specific verb+resource ('Confirm the email') and explicitly covers the two distinct modes (code entry vs. polling for a clicked link). An agent can distinguish this from siblings like resend_code or create_api_key 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 names the preferred invocation, the alternative invocation, the polling cadence and ceiling (every 5 seconds, up to 10 minutes until email_verified is true), the follow-up call (create_api_key), and the escalation path (resend_code) when the code is exhausted. When/when-not guidance is fully explicit.

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.