Skip to main content
Glama
RPasquale

lightbulb-mcp

by RPasquale
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

page_builder_create

Create a new page builder session to design a website or landing page, returning a session ID for iterative building.

Instructions

Create a new page builder session to build a website or landing page.

Returns a session ID you can use with page_builder_chat to iteratively design and build pages.

Args: brand_name: The brand/company name for the site initial_prompt: Optional initial instruction (e.g. "Build a landing page for our SaaS product") coding_harness: Required when the prompt is routed into a new consulting project. force_page_builder: If true, create a pure Page Builder design session instead of routing project-build intent to consulting workflow.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brand_nameNo
coding_harnessNo
initial_promptNo
force_page_builderNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / coding_harness
      Added value: +{
+  "default": "",
+  "title": "Coding Harness",
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With zero annotations, the description carries the disclosure burden and largely meets it: it declares the return contract (session ID usable with page_builder_chat), the non-obvious routing behavior (consulting workflow vs. page builder mode), and the condition under which coding_harness matters. It does not disclose cost, session limits, or cleanup behavior, but the described side effects are materially covered.

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?

Two purpose/return sentences front-load the intent, followed by a tight four-line Args block that adds value the schema lacks (0% coverage). Nothing is wasted, and the example in initial_prompt earns its place by clarifying a free-text field.

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

Completeness4/5

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

An output schema exists, so the return-value burden is lowered, and the description still states the session-ID usage. Given four simple, optional parameters with full descriptions and clear routing behavior, the picture is fairly complete. The main missing piece is broader lifecycle/side-effect context (session limits, cost, deletion), which is acceptable but not ideal for a creation tool.

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 description coverage is 0%, so the description must compensate, and it does meaningfully for all four parameters: brand_name and initial_prompt get plain-language definitions (with an example), force_page_builder gets a precise routing contract, and coding_harness gets its triggering condition. The only residual gap is that coding_harness's actual value semantics (what a harness identifier is) remain unexplained.

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 is a specific verb+resource pair ('Create a new page builder session... to build a website or landing page') and names the companion tool page_builder_chat that consumes its return value, which helps the agent distinguish this creation step from chat, list, preview, and deploy siblings. It does not enumerate exclusions against every sibling, but the stated create-session scope is unmistakable.

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 description embeds real 'when vs. alternative' guidance by explaining that prompts may be routed into a consulting workflow and that force_page_builder overrides that routing for a pure Page Builder session, with coding_harness marked required in the consulting path. It lacks an explicit 'use this instead of X when...' sentence, but the routing alternatives are clear enough for an agent to decide.

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

Deploy Server

Other Tools