Get a standalone product landing page as self-contained HTML with inline CSS, no external assets, scripts, or tracking. Use it for reliable offline or embedded rendering.
Get the standalone product landing page as HTML (self-contained, no external assets).
The HTML renders from the same verified catalog as every other tool: inline CSS, no CDN, no scripts, no tracking.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Since no annotations are provided, the description carries the full burden of behavioral disclosure. It explicitly states the output is self-contained with inline CSS, no CDN, no scripts, and no tracking, adding useful context about the HTML contents beyond the tool name.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the main action and key attribute. Every sentence contributes value, and there is no wasted wording.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with no parameters and no output schema, the description provides essential details about the return type (HTML) and its characteristics. It does not mention error conditions or fallback behavior, but for a simple retrieval tool this is sufficient.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With zero parameters, the baseline is 4. The description adds no parameter information, but none is needed since the schema is empty and there is nothing to explain.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb 'Get' with a clear resource 'standalone product landing page as HTML' and adds the distinguishing characteristic 'self-contained, no external assets.' This clearly separates it from sibling tools that return components or lists, such as get_component or list_components.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no explicit guidance on when to use this tool versus alternatives. It mentions the HTML renders from the same verified catalog as other tools, but does not specify conditions or scenarios where this tool is preferred, leaving the agent to infer usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.