TheySaid

Prepare design snapshot

prepare_design_snapshot

Creates an upload slot for a self-contained design (HTML) so TheySaid's AI testers can run a usability test on it. Suited to designs without a durable public URL, such as a Claude Design or Artifact. Temporary preview links (for example claudeusercontent.com) expire during a test, so they are not suitable as prototypeUrl. Live apps built with v0, Lovable, Bolt or Replit are better tested through their published public URL, because a snapshot of them loses styling. The design HTML is temporarily uploaded to TheySaid. Returns { uploadId, uploadUrl, expiresInSeconds, nextStep }. Upload the HTML (text/html, CSS/JS inlined, large assets on absolute CDN URLs) with one PUT to uploadUrl, or with upload_design_snapshot when the environment blocks that host. Then: check_design_snapshot, followed by propose_usability_test(uploadId) for a new test or relaunch_usability_test(projectId, uploadId) to re-test an existing project. This tool does not start a test. Snapshots suit static designs and click-through prototypes; apps that need a live backend or login need a reachable public URL.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "prepare_design_snapshot"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`nextStep`	No	Guidance: upload → check → propose/relaunch → review → launch.
`uploadId`	No	Opaque handle for check_design_snapshot / propose / relaunch.
`uploadUrl`	No	Presigned PUT URL to upload the self-contained design HTML.
`expiresInSeconds`	No	Seconds the presigned PUT stays valid.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 16, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false, openWorldHint=false), the description discloses that HTML is temporarily uploaded to TheySaid, that the snapshot expires, the exact return shape, and that this tool does NOT start a test. It also states the sequencing with check_design_snapshot and propose/relaunch tools.

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 routing decision and limitations are front-loaded and each sentence carries a constraint or next step. It is somewhat long for a no-parameter tool, but no sentence is pure filler.

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 values need not be explained, yet the description still names { uploadId, uploadUrl, expiresInSeconds, nextStep } and lays out the full follow-up workflow. For an agent needing to call this correctly, nothing essential 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?

The tool takes zero parameters, so the schema baseline is 4. The description still adds value by documenting the upload contract (text/html, inlined CSS/JS, absolute CDN URLs) even though that lives at the uploadUrl stage rather than in an input parameter.

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 opens with a specific verb+resource: 'Creates an upload slot for a self-contained design (HTML)'. It names the purpose (usability testing by TheySaid AI testers) and clearly distinguishes itself from siblings like upload_design_snapshot and propose_usability_test.

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?

Gives explicit when-to-use (designs without a durable public URL, Claude Design/Artifact), when-not-to-use (expiring claudeusercontent.com links, live v0/Lovable/Bolt/Replit apps that lose styling in a snapshot), and alternatives (published public URL, upload_design_snapshot). Nothing is left to inference.

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

All TheySaid 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.

Resources

Need Help?