Skip to main content
Glama
vuluu2k

sbuilder-mcp

by vuluu2k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

sb_import_site

Read a whole site from one URL and generate draft pages for each found page, built with your site's tokens. Use dry run to preview the page list before creation.

Instructions

Read a WHOLE site from one URL — its sitemap, or the links on that page — and give each page found its own DRAFT page here, built from this site's tokens. Not a clone. Dry run returns the page list before anything is created.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
navNoShared header linking the new pages, default true
urlYesAny page of the site
depthNoNo sitemap: link depth, default 1
themeNoPatch this site's theme from the entry page's colours and type scale, default true — SITE-WIDE, affecting pages outside this import too
dry_runNo
excludeNo
includeNoPath substrings to keep
site_idNo
homepageNoEntry into this site's home page, default true
max_nodesNoPer page. No cap by default
max_pagesNoDefault 12
max_imagesNoDefault 24, whole import
upload_imagesNo
nav_timeout_msNoHow long to wait for a page to answer at all. Default 30000; raise it for a slow origin

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.41.0
    • changedInput schema / properties / max_nodes / description
      Previous value: -"Per page, default 300"New value: +"Per page. No cap by default"
    • removedInput schema / properties / max_nodes / maximum
      Removed value: -1000
    • addedInput schema / properties / theme
      Added value: +{
+  "description": "Patch this site's theme from the entry page's colours and type scale, default true — SITE-WIDE, affecting pages outside this import too",
+  "type": "boolean"
+}
  2. Changed1 schema field changedv0.39.0
    • addedInput schema / properties / nav_timeout_ms
      Added value: +{
+  "description": "How long to wait for a page to answer at all. Default 30000; raise it for a slow origin",
+  "maximum": 120000,
+  "minimum": 5000,
+  "type": "integer"
+}
  3. Addedv0.25.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false (so the agent knows it mutates) and openWorldHint=true. The description adds valuable context beyond annotations: 'Dry run returns the page list before anything is created', clarifying the dry_run side effect, and 'Not a clone' sets expectations about output nature. However, it doesn't address permissions required, rate limits, or what happens to the site's existing pages (creation vs. overwrite), leaving some mutation risk opaque.

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 two concise sentences that front-load the core action ('Read a WHOLE site from one URL') and then add the dry run note. It's efficient with no fluff, though the second sentence is a fragment that could be integrated more smoothly.

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 14-parameter, mutation-heavy tool with no output schema and 71% schema coverage, the description is somewhat thin. It doesn't explain return values beyond the dry run case, doesn't mention failure modes or whether existing pages are affected, and omits guidance on common pitfalls like theme being 'SITE-WIDE'. It's adequate but leaves notable gaps.

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 coverage is 71%, so the schema covers most parameters, but several key parameters lack descriptions (e.g., dry_run, exclude, upload_images, site_id). The description adds meaning for the overall import behavior (sitemap vs. link crawling, draft creation) but doesn't compensate for the gaps in the schema's parameter documentation, such as the exact format of include/exclude paths or the effect of site_id.

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+resource ('Read a WHOLE site from one URL' and 'give each page found its own DRAFT page'), and clearly distinguishes the tool from the sibling 'sb_import' by specifying site-level reading. It's clear what the tool does, though the phrase 'built from this site's tokens' is a bit jargon-heavy and 'Not a clone' adds ambiguity about what exactly is produced.

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 versus alternatives like sb_import or sb_page_create. It mentions dry run behavior but doesn't say when to prefer this over a single-page import or manual page creation. No exclusions or prerequisites are mentioned.

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