Skip to main content
Glama

Mimiq: test pages and copy on simulated people

by io.github.victorgulchenko
OverviewDiscussionsAdmin

mimiq.test_page

Read-only

Show a web page to simulated people and hear how they react: who would stay, who would leave, and why. Each person scrolls the page and says what confused them, what they doubted and what would change their mind. Use it after you build or change a landing, pricing or signup page, then fix what they raised and test again. Needs a public URL (for localhost, open a tunnel first; see the server instructions). Returns each person's action, thoughts and objections, and the counts. With a key, the result ends with a link to the full report in the Mimiq app.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe page to test. Must be publicly reachable. For localhost, open a cloudflared tunnel and pass the tunnel URL.
goalNoWhat the page should get people to do, e.g. "sign up for the waitlist".
countNoHow many simulated people (default 10, max 50). Each person uses one credit.
audienceNoWho 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.
timeout_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • 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 10, max 50). More = higher confidence but slower."New value: +"How many simulated people (default 10, max 50). Each person uses one credit."
    • changedInput schema / properties / goal / description
      Previous value: -"What the page is trying to achieve, e.g. \"get visitors to sign up for the waitlist\". Providing a goal helps personas evaluate the page against a specific conversion objective."New value: +"What the page should get people to do, e.g. \"sign up for the waitlist\"."
    • changedInput schema / properties / url / description
      Previous value: -"The URL to test. Must be publicly accessible. For localhost, first create a cloudflared tunnel and pass the tunnel URL here."New value: +"The page to test. Must be publicly reachable. For localhost, open a cloudflared tunnel and pass the tunnel URL."
  2. Changed6 schema fields changed
    • 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, auto-detects from page content."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 the page is trying to achieve, e.g. \"get visitors to sign up for the waitlist\"."New value: +"What the page is trying to achieve, e.g. \"get visitors to sign up for the waitlist\". 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
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

The annotations already mark the tool as read-only and non-destructive, and the description adds substantial behavioral context: simulated people scroll, voice confusions/doubts, and the call returns actions, thoughts, objections, and counts. It also discloses the public URL requirement and the optional report link with a key, enriching the agent's understanding beyond the structured annotations.

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?

The description is front-loaded with the core purpose and then provides usage guidance, prerequisites, and output expectations. Each sentence adds useful information, though some phrases like 'who would stay, who would leave, and why' are illustrative rather than strictly necessary.

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?

The description covers the tool's purpose, when to use it, prerequisite URL handling, and the high-level output shape, which is especially valuable since there is no output schema. It does not need to restate all parameter details because the schema is well documented, but it could have been slightly more explicit about how goals and audiences influence the test.

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 80%, so the schema already explains most parameters. The description adds little beyond what the schema provides for the url parameter (public reachability and tunnel), and it does not add meaning for goal, count, audience, or timeout_seconds. This is acceptable given the high baseline but not a standout.

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 description clearly identifies the tool's job: show a web page to simulated people and collect their reactions, including who stays, who leaves, and why. This distinguishes it from the sibling tools, which target components, copy, text, flows, or audience research rather than full-page reactions.

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?

The description explicitly says when to use it: 'after you build or change a landing, pricing or signup page, then fix what they raised and test again.' It also notes the public-URL prerequisite and localhost tunnel alternative. It does not explicitly name sibling tools or when not to use it, so it stops short of a 5.

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 copy on simulated people toolsInspect
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.

Resources