Mimiq: test pages and sign-up flows on simulated people

Test a flow

mimiq.test_flow

Starts immediately unless the recruited crowd is wrong (more than 1 in 5 not the requested audience) or the page could not be read to check its market; the result includes the audience summary, examples and fit. Only those return audience_review: show the warning, then use review_id, confirm_audience and audience_fit_acknowledged to continue, or audience_correction to recruit again. Send simulated people through a multi-step flow (signup, onboarding, checkout) in a real browser, clicking and typing, to find the step where they get stuck or give up. Slower than test_page, and each person uses 5 credits. Returns each person's steps, where they stopped and why.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	Where the flow starts. Must be publicly reachable. For localhost, open a cloudflared tunnel and pass the tunnel URL.
`goal`	No	The task each person tries, e.g. "complete the signup and reach the dashboard". Default: sign up and start using it.
`count`	No	How many simulated people (default 5, max 10; without a key a free flow has up to 3, and defaults to 3). Each runs a full browser session and uses 5 credits.
`audience`	No	Who the simulated people should be, in plain words, e.g. "startup founders in SF" or "parents shopping for kids toys". If omitted, Mimiq picks the likely audience from the content.
`max_steps`	No	Optional step limit per person (10 to 60). The server defaults to 40.
`review_id`	No	The review_id from a low-fit review or completed/running result. Bound to this URL and test kind.
`timeout_seconds`	No
`confirm_audience`	No	Start with the reviewed people after showing them to the user.
`audience_correction`	No	Not quite? Change who and rerun: use with review_id. Recruits a new crowd under the existing credit rules; starts unless the new crowd is wrong, otherwise returns a new review.
`audience_fit_acknowledged`	No	Set only after telling the user about an audience-fit warning and they choose to continue.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`run`	No
`call`	No
`tool`	Yes
`status`	No
`report_url`	No
`summary_card`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 30, 2026

changedInput schema / properties / audience_correction / description

Previous value: -"Not quite? Change who and rerun: use with review_id. Recruits a new crowd under the existing credit rules; starts at 80% fit or more, otherwise returns a new review."New value: +"Not quite? Change who and rerun: use with review_id. Recruits a new crowd under the existing credit rules; starts unless the new crowd is wrong, otherwise returns a new review."

changedInput schema / properties / audience_fit_acknowledged / description

Previous value: -"Set only after telling the user about a below-80% fit warning and they choose to continue."New value: +"Set only after telling the user about an audience-fit warning and they choose to continue."

Changed1 schema field changedSep 30, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "call": {
+      "additionalProperties": true,
+      "properties": {
+        "headline": {
+          "type": "string"
+        },
+        "pick": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "reason": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "report_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "run": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "status": {
+      "type": "string"
+    },
+    "summary_card": {
+      "type": "string"
+    },
+    "tool": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "tool"
+  ],
+  "type": "object"
+}

Changed4 schema fields changedSep 30, 2026

addedInput schema / properties / audience_correction

Added value: +{
+  "description": "Not quite? Change who and rerun: use with review_id. Recruits a new crowd under the existing credit rules; starts at 80% fit or more, otherwise returns a new review.",
+  "maxLength": 1500,
+  "type": "string"
+}

addedInput schema / properties / audience_fit_acknowledged

Added value: +{
+  "description": "Set only after telling the user about a below-80% fit warning and they choose to continue.",
+  "type": "boolean"
+}

addedInput schema / properties / confirm_audience

Added value: +{
+  "description": "Start with the reviewed people after showing them to the user.",
+  "type": "boolean"
+}

addedInput schema / properties / review_id

Added value: +{
+  "description": "The review_id from a low-fit review or completed/running result. Bound to this URL and test kind.",
+  "maxLength": 100,
+  "type": "string"
+}

Changed1 schema field changedSep 30, 2026
- changedInput schema / properties / timeout_seconds / default
```
Previous value: -900New value: +1200
```
Changed5 schema fields changedSep 30, 2026
- removedInput schema / properties / max_steps / default
```
Removed value: -15
```
- changedInput schema / properties / max_steps / description
```
Previous value: -"Most steps per person (default 15)."New value: +"Optional step limit per person (10 to 60). The server defaults to 40."
```
- changedInput schema / properties / max_steps / maximum
```
Previous value: -100New value: +60
```
- changedInput schema / properties / max_steps / minimum
```
Previous value: -1New value: +10
```
- changedInput schema / properties / timeout_seconds / default
```
Previous value: -420New value: +900
```

Changed1 schema field changedSep 29, 2026

changedInput schema / properties / count / description

Previous value: -"How many simulated people (default 5, max 10; without a key a free flow has up to 3, and defaults to 3). Each runs a full browser session and uses 30 credits."New value: +"How many simulated people (default 5, max 10; without a key a free flow has up to 3, and defaults to 3). Each runs a full browser session and uses 5 credits."

Changed1 schema field changedSep 24, 2026

changedInput schema / properties / count / description

Previous value: -"How many simulated people (default 5, max 10; without a key a free flow has up to 3, and defaults to 3). Each runs a full browser session and uses 10 credits."New value: +"How many simulated people (default 5, max 10; without a key a free flow has up to 3, and defaults to 3). Each runs a full browser session and uses 30 credits."

Changed2 schema fields changedSep 24, 2026

changedInput schema / properties / count / description

Previous value: -"How many simulated people (default 5, max 10). Each runs a full browser session and uses 10 credits."New value: +"How many simulated people (default 5, max 10; without a key a free flow has up to 3, and defaults to 3). Each runs a full browser session and uses 10 credits."

changedInput schema / properties / goal / description

Previous value: -"What success looks like, e.g. \"complete the signup and reach the dashboard\"."New value: +"The task each person tries, e.g. \"complete the signup and reach the dashboard\". Default: sign up and start using it."

Changed5 schema fields changedSep 24, 2026

changedInput schema / properties / audience / description

Previous value: -"Who should test this page. Natural language, e.g. \"startup founders in SF\" or \"parents shopping for kids toys\". If omitted, Mimiq auto-detects the likely audience from page content."New value: +"Who the simulated people should be, in plain words, e.g. \"startup founders in SF\" or \"parents shopping for kids toys\". If omitted, Mimiq picks the likely audience from the content."

changedInput schema / properties / count / description

Previous value: -"Number of simulated users (default 5, max 10). Each runs a full interactive browser session."New value: +"How many simulated people (default 5, max 10). Each runs a full browser session and uses 10 credits."

changedInput schema / properties / goal / description

Previous value: -"What success looks like, e.g. \"complete the signup and reach the dashboard\". Providing a goal helps personas evaluate the page against a specific conversion objective."New value: +"What success looks like, e.g. \"complete the signup and reach the dashboard\"."

changedInput schema / properties / max_steps / description

Previous value: -"Maximum navigation steps per persona (default 15)."New value: +"Most steps per person (default 15)."

changedInput schema / properties / url / description

Previous value: -"Starting URL of the flow to test. For localhost, first create a cloudflared tunnel and pass the tunnel URL here."New value: +"Where the flow starts. Must be publicly reachable. For localhost, open a cloudflared tunnel and pass the tunnel URL."

Changed6 schema fields changedMar 17, 2026

changedInput schema / properties / audience / description

Previous value: -"Target audience description. E.g. \"small business owners looking for accounting software\"."New value: +"Who should test this page. Natural language, e.g. \"startup founders in SF\" or \"parents shopping for kids toys\". If omitted, Mimiq auto-detects the likely audience from page content."

addedInput schema / properties / audience / maxLength
```
Added value: +500
```

removedInput schema / properties / bridge_id

Removed value: -{
-  "description": "Deprecated. Use cloudflared tunnel directly instead.",
-  "type": "string"
-}

changedInput schema / properties / goal / description

Previous value: -"What success looks like, e.g. \"complete the signup and reach the dashboard\"."New value: +"What success looks like, e.g. \"complete the signup and reach the dashboard\". Providing a goal helps personas evaluate the page against a specific conversion objective."

addedInput schema / properties / goal / maxLength
```
Added value: +500
```
addedInput schema / properties / url / maxLength
```
Added value: +2000
```

First observedMar 15, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnly=false, idempotent=false, openWorld=true. The description adds real context beyond that: the audience-fit gate ('more than 1 in 5 not the requested audience'), the credit cost per person, the slower-than-test_page trait, and the audience_review continuation protocol. It doesn't mention timeout behavior, but the schema covers timeout_seconds.

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

Conciseness2/5

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

The description opens with a dense, hard-to-parse sentence about audience gating ('Starts immediately unless the recruited crowd is wrong...') before it ever says what the tool does. The core purpose is buried in sentence two. Several clauses about review_id/confirm_audience/audience_correction duplicate the schema descriptions and could be trimmed.

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?

For a complex, 10-parameter, open-world tool with an output schema, the description covers cost, speed relative to peers, audience-review branch handling, and what is returned (steps, where they stopped and why). Missing explicit timeout guidance and a tie-breaker against other flow-related siblings, but substantially complete.

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 coverage is 90%, so the parameters are already well documented in the schema. The description reinforces the purpose of goal/max_steps implicitly but mostly restates the audience-review flow rather than adding syntax or format meaning for url, count, or timeout. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description uses a specific verb and resource: 'Send simulated people through a multi-step flow ... in a real browser, clicking and typing, to find the step where they get stuck or give up.' It clearly distinguishes the tool from test_page ('Slower than test_page'), though it is oddly front-loaded with audience-gating mechanics before the core purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names test_page as a faster alternative and the cost trade-off ('each person uses 5 credits'), which implies when to prefer the page tool. But it never explicitly states when to use this flow tool versus siblings like compare_urls or test_component, and the usage instructions are tangled in the audience-review branch logic.

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

All Mimiq: test pages and sign-up flows on simulated people 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.

Test a flow

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources