webEmbedding

Plan Reproduction Path

plan_reproduction_path

Read-onlyIdempotent

Create a source-first plan that separates exact embed/source reuse from local capture and bounded rebuild work.

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": "plan_reproduction_path"
  }
}

Input Schema

Name	Required	Description
`candidates`	No	Embed/source candidates as returned by discover_embed_candidates (objects with kind and url).
`license_text`	No	License or permission text that allows reusing the page, from the user or the site; informs the reuse/rebuild policy.
`site_profile`	No	The site_profile object returned by inspect_url.
`capture_bundle`	No	Capture bundle from the local MCP's capture_reference_bundle, if one exists.
`source_signals`	No	Extra hints about the page's origin, e.g. ["framer", "spline", "export"]; merged with signals detected from the page.
`exact_requested`	No	True (default) when the user wants an exact, faithful clone; false when an approximate rebuild is acceptable.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 8, 2026

addedInput schema / properties / candidates / description

Added value: +"Embed/source candidates as returned by discover_embed_candidates (objects with kind and url)."

addedInput schema / properties / capture_bundle / description

Added value: +"Capture bundle from the local MCP's capture_reference_bundle, if one exists."

addedInput schema / properties / exact_requested / description

Added value: +"True (default) when the user wants an exact, faithful clone; false when an approximate rebuild is acceptable."

addedInput schema / properties / license_text / description

Added value: +"License or permission text that allows reusing the page, from the user or the site; informs the reuse/rebuild policy."

addedInput schema / properties / site_profile / description

Added value: +"The site_profile object returned by inspect_url."

addedInput schema / properties / source_signals / description

Added value: +"Extra hints about the page's origin, e.g. [\"framer\", \"spline\", \"export\"]; merged with signals detected from the page."

AddedOct 28, 2026
RemovedAug 26, 2026
First observedMay 8, 2026

TDQS

B3.2/5.0

Behavior3/5

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

The annotations already establish that this is read-only, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds the useful behavioral trait that the plan prioritizes source reuse and separates exact reuse from capture/rebuild work, but it does not elaborate on planning logic, assumptions, or edge cases.

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 a single front-loaded sentence with no filler. It is concise and structurally sound, though its density and specialized wording make it slightly less immediately clear than it could be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With six parameters, nested objects, and an output schema, the definition is minimally sufficient because the schema and output schema carry most of the structural detail. However, the description does not explain how the inputs combine into a plan or when this tool should be invoked relative to its siblings, leaving a meaningful workflow gap.

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 100%, so all six parameters are already documented in the input schema. The tool description itself adds no additional parameter-level meaning beyond the high-level phrase about separating reuse from rebuild work, which makes the baseline score appropriate.

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 states a specific verb and resource: create a plan that separates exact embed/source reuse from local capture and rebuild work. It is clear enough to distinguish this planning tool from sibling tools like discover_embed_candidates and generate_embed_snippet, though terms such as "source-first" and "bounded rebuild work" are somewhat jargon-heavy.

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

Usage Guidelines2/5

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

The description gives no explicit when-to-use guidance, prerequisites, or comparison with sibling tools. An agent can infer that this is a planning step after candidate discovery and URL inspection, but that inference comes from the schema parameter descriptions rather than the tool description itself.

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

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