Skip to main content
Glama

boomurl

by com.boomurl

publish_site

Create or update (idempotent) a static site the key owns. files maps relative path -> file contents. No index.html required — a lone .md/.txt/.pdf becomes a page; index.html is the front door when present. Returns the live URL. Requires a key from create_publish_key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesboom_sk_ key from create_publish_key.
nameYesSite name (lowercase slug).
filesYesMap of relative path -> file contents (UTF-8, or base64 when base64=true).
base64NoTreat file values as base64 (for binary files like images).

TDQS

A4.6/5.0
Behavior5/5

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

Discloses idempotency, file handling rules (index.html behavior), return value (live URL), and authentication requirement. No annotations provided, so description carries full burden and does so thoroughly.

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?

Three sentences, front-loaded with purpose, then details, then return and requirement. No redundant information.

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?

Covers purpose, parameters, return, and prerequisite. No output schema, but return is described. Missing error conditions or rate limits, but sufficient for the tool's modest complexity.

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 100%, baseline 3. Description adds meaning: explains key source, name requirement, file mapping, and base64 parameter. Extra context beyond schema schemas present.

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?

Clearly states it creates or updates a static site, is idempotent, and explains file mapping. Distinguishes from sibling tools by referencing prerequisite key from create_publish_key.

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?

Describes when to use (create/update static site) and prerequisite (key from create_publish_key). Lacks explicit comparisons or when-not-to-use, but context from sibling tools makes it clear.

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

All boomurl toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation5/5

All 14 tools have clearly distinct purposes with no overlap. Related tools like buy_credits, get_balance, and list_topup_packs handle different aspects of credit management without ambiguity.

Naming Consistency5/5

Tool names follow a consistent verb_noun pattern with snake_case (e.g., attach_domain, delete_site, list_sites). No mixing of conventions.

Tool Count5/5

14 tools cover the core functionality of a static site hosting service: domain management, site publishing/deletion, credit system, key acquisition, and name checking. The scope is well-balanced.

Completeness4/5

The tool set covers the main lifecycle (create, read, update, delete) for sites and domains. Minor gaps include no direct tool to rename a site or manage keys beyond creation.

Resources