killbottleneck-mcp

Official

Overview Schema Source Related Servers Discussions Admin

create_page

Creates a sandboxed page from a complete single-file HTML document, shows it in the user's Pages panel, and optionally makes it visible to the organization.

Instructions

Create a page from a COMPLETE single-file HTML document you wrote yourself (inline CSS/JS; external libraries only from https CDNs; no fetch to other servers; size limit per instance, typically 300 kB). The page appears in the user's Pages panel in the app and runs sandboxed (no access to the app's session). team_visible=true shows it to all members of the organization. Returns the id and the public link if one is on.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>",
      "html": "<html>"
    },
    "name": "create_page"
  }
}

Input Schema

Name	Required	Description
`html`	Yes	the whole HTML document
`title`	Yes
`team_visible`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.0.1Nov 9, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses sandboxing, no access to the app session, https-CDN-only libraries, no fetch to other servers, a ~300 kB size limit, team_visible semantics, and the return values. It stops short of stating permission requirements or failure behavior, so it is strong but not exhaustive.

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?

Dense but front-loaded: the core action comes first, followed by content constraints, sandbox behavior, visibility, and return value. The nested parenthetical about CDNs and fetch is slightly cramped but every clause carries information.

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?

For a 3-parameter creation tool with no annotations and no output schema, the description covers the essential behavioral context (sandbox, size, visibility, returned id/link). It stops short of stating prerequisites such as required permissions or the default value of team_visible when omitted, leaving a modest gap.

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?

Schema coverage is only 33% (only html has a schema description), so the description must compensate. It clarifies the html content constraints and explains what team_visible=true does; only title remains purely implicit (obvious enough), which is a small gap.

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 concrete verb+resource ('Create a page') and immediately qualifies the expected input as a complete single-file HTML document, which cleanly separates it from sibling tools like update_page, get_page, and share_page.

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

Usage Guidelines3/5

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

The description implies when this tool is appropriate by requiring a self-authored complete HTML document, but it never names alternatives or states exclusions (e.g., when to use update_page instead of re-creating, or how sharing relates to share_page).

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