Run MCP
Pick a tool from the live list, fill the form, and run it.
- Endpoint
- POST https://www.blackboxpersonalization.com/api/mcp
- Protocol
- 2026-07-28
- Server
- black-box 1.0.0
Also accepts 2025-11-25 and 2025-06-18 when the client asks.
Result
Run a tool to see the result.
Request
Waiting for a run.
Response
Waiting for a run.
Connect
Cursor and Claude Desktop use mcpServers. VS Code uses servers. The same url.
{
"mcpServers": {
"black-box": { "url": "https://www.blackboxpersonalization.com/api/mcp" }
}
}{
"servers": {
"black-box": { "url": "https://www.blackboxpersonalization.com/api/mcp" }
}
}Understanding the labHow to use it and why you'd want to
Why you'd want to
You want to call one tool yourself and read the JSON-RPC. Catalog tools return public fields from this site.
How to use it
- Pick a tool. The form follows its schema.
- Run it. Read the request and the response.
- Accept if you want the tool name queued.
- Leave the question text out of the event.
WalkthroughHow we built itShowHide
Example vendor setup is marked below. eVar and event numbers are examples. This lab does not call Adobe.
The playground lists tools from /api/mcp and runs one call. After Accept it queues mcp_playground_called with the tool name only. Typed text is not logged. The lab does not call Adobe.
Show the example
The shared MCP view renders the request, the response, the timeline, and the answer. The trace is labeled as an example.
Stay read-only
Navigation and tools stay on this origin. There is no form submit and no write tool.
Queue the name only
After Accept, demonstrateEvent sends the lab event. When a tool ran, the only parameter is tool. The question text is not a parameter.
Skip the event before Accept
The Next button still moves the example when consent is off. demonstrateEvent returns without pushing.
From the code
After Accept, the step queues its event. A tool name is the only extra field.
function go(next: number) {
const target = steps[next]
if (!target) return
setIndex(next)
const eventName = target.event
if (granted && eventName) {
const tool = target.tool
demonstrateEvent(eventName, tool ? { tool } : {})Consent off still lets the example move. The event is skipped.
{granted ? null : (
<p className="mt-3 rounded-lg border px-3 py-2 text-sm">{tr(locale, "Accept measurement to record the step. The example still moves. Nothing is pushed before Accept.", "Acepta la medición para registrar el paso. El ejemplo igual avanza. No se envía nada antes de Aceptar.")}</p>Google and Adobe
Google queues mcp_playground_called after Accept. Adobe is an example of the same fields.
After Accept, this lab queues mcp_playground_called. When a tool ran, the parameter is tool and nothing else. The question and the answer text are not parameters. This site does not call gtag('set') or Adobe.
Simplified shape of the object queued after Accept. Register any new parameter as an event-scoped custom dimension. This site does not call gtag('set').
dataLayer.push({
event: "mcp_playground_called",
tool: "list_labs",
})Example implementation. This site does not call Adobe. eVar123, prop123, and event123 are example variable numbers. In Launch, a data element reads the value and a rule sends it when the value changes. In the report suite, enable eVar123 with Most Recent allocation and expire it on the hit. A processing rule is unnecessary if the data element maps straight to that eVar.
Example alloy payload. _example is a placeholder schema, not a real tenant.
alloy("sendEvent", {
xdm: {
eventType: "web.webinteraction.linkClicks",
_example: {
mcpTool: "list_labs",
},
},
})Example hit. eVar123 is hit-scoped in this example. prop123 dies at the same hit.
s.eVar123 = "list_labs"
s.prop123 = "list_labs"
s.events = "event123"
s.linkTrackVars = "eVar123,prop123,events"
s.linkTrackEvents = "event123"
s.tl(true, "o", "mcp_playground_called")Translation
Each lab field, the GA4 name, and the example Adobe variable. Scope is the part that usually gets lost in the translation.
Step
GA4. Event mcp_playground_called after Accept.
Adobe. Example event123. This site does not call Adobe.
Scope. Event. It records that the step was shown.
Tool name
GA4. Parameter tool. The arguments are not sent.
Adobe. Example eVar123, expire on the hit. This site does not call Adobe.
Scope. Event. A user property would keep the last tool.
Question text
GA4. Not sent.
Adobe. Do not put the question in a prop. Not sent.
Scope. It stays on the page.
Consent
GA4. Not a parameter. The push is skipped until Accept.
Adobe. Example: skip the hit while consent is off.
Scope. A gate on the hit.
Recommended next
Why these picksReading path transitions…