Menso

Get a Menso replay link

get_replay_link

Idempotent

Create, or return the existing, public replay link for a finished Menso test: a menso.io/r/... page that shows every step the AI user took and what they thought. Anyone with the link can watch it, so share it deliberately. Included in the Pro and Studio plans; on Free it returns an upgrade note instead of a link.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`test_id`	Yes	The test_id returned by run_test.

Output Schema

TableJSON Schema

Name	Required	Description
`plan`	No
`test_id`	Yes
`share_url`	No
`upgrade_url`	No
`identity_hits`	No	How often the replay shows the test account's email or username (it does not block the link).
`plan_upgrade_required`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 2, 2026

addedOutput schema / properties / identity_hits

Added value: +{
+  "description": "How often the replay shows the test account's email or username (it does not block the link).",
+  "type": "integer"
+}

First observedSep 29, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond annotations by disclosing the consequential side effect: the link is public, anyone can watch it, and it should be shared deliberately. It also explains the plan-based fallback behavior (upgrade note instead of a link). This is consistent with readOnlyHint=false and idempotentHint=true rather than contradicting them.

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?

Three sentences, front-loaded with the core action, then the sharing warning, then the plan caveat. Every sentence adds decision-relevant information with no padding.

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?

With an output schema present, return values need not be described; the description instead covers the things structured fields cannot: public exposure, sharing caution, and plan-dependent outcomes. Nothing needed to invoke correctly is missing.

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 100% for the single test_id parameter, including its pattern and provenance (returned by run_test), so the schema carries the parameter burden. The description adds no syntax or format detail, so baseline 3 is appropriate.

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?

States a specific verb and resource ('Create, or return the existing, public replay link for a finished Menso test') and pins the scope to finished tests. An agent can distinguish this from run_test, get_status, and get_findings 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 Guidelines4/5

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

The precondition (a finished test) and the plan gating (Pro/Studio gets a link, Free gets an upgrade note) tell the agent when the call is appropriate and what to expect otherwise. No sibling alternative is named, but the siblings are unrelated operations, so no explicit exclusion is needed.

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

All Menso tools Inspect

Try in Browser

Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.