Skip to main content
Glama

Blawgy

by com.blawgy
OverviewDiscussionsAdmin

Create a site

create_site
Destructive

Step 2 of adding a site: registers the domain under the caller's account with the business description, audience, tone, competitors and business type (usually the values from analyze_new_site, edited as needed). Returns the site key and what billing needs: partner-billed and comped accounts are ready at once; a direct customer must finish checkout in the browser (the response includes the link; pass plan + billingPeriod to get a direct Stripe checkout URL). White-label partners on a partner-scoped credential can pass clientId (from create_client or list_clients) to create the site for that client instead: it belongs to the client, is billed to the partner, and plan/billingPeriod are refused. Then call complete_site_setup to pick publish mode and build the first content plan. Fails with 409 if the domain belongs to another account. Keys accepted in market: countryCode, locationName, languageCode. Keys accepted in businessProfile: businessName, address, city, state, postalCode. Destructive: the first call returns a summary and a confirmToken; call again with confirmToken to proceed.

Input Schema

NameRequiredDescriptionDefault
planNoFor direct customers: create a Stripe checkout for this plan and return its URL.
toneYesWriting tone, e.g. "Friendly and approachable".
domainYesThe website, e.g. example.com.
marketNoSearch market, e.g. {countryCode:"US", locationName:"United States", languageCode:"en"}. From analyze_new_site.
clientIdNoWhite-label partners only: create the site for this client (client id or email from create_client / list_clients). Needs a partner-scoped credential.
faviconUrlNoFavicon from analyze_new_site.
competitorsNoCompetitor domains to mine for keywords.
businessTypeNoKeyword research mode (default general).
confirmTokenNoConfirmation token from a previous call of this tool with the same arguments. Omit on the first call to get a summary and a token.
billingPeriodNoWith plan (default annual).
targetAudienceYesCustomer segments the content is for.
businessProfileNoPrimary physical location for local businesses (from analyze_new_site locations).
productDescriptionYesWhat the business does and sells.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / clientId
      Added value: +{
+  "description": "White-label partners only: create the site for this client (client id or email from create_client / list_clients). Needs a partner-scoped credential.",
+  "maxLength": 254,
+  "minLength": 1,
+  "type": "string"
+}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well past the annotations by describing what actually happens: the first call returns only a summary and confirmToken (consistent with destructiveHint=true), the second commits; billing outcomes differ by account type; the response carries a Stripe checkout URL and the site key; cross-account domains fail with 409.

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?

Front-loaded with the workflow role and the core action, and nearly every clause carries unique operational detail. It is nonetheless a single dense block covering workflow, billing, scoping, error codes and confirmation semantics — splitting it into short labeled sections would cost bandwidth but improve scannability.

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

Completeness5/5

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

For a 13-parameter mutation with nested objects and no output schema, the description covers the return value (site key plus billing state/applicable link), the confirmation protocol, credential scoping, and the expected error — nothing an agent needs before invoking it is missing.

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%, so the baseline is 3, but the description adds governing rules the schema cannot express — that plan and billingPeriod must be passed together, that clientId comes from create_client/list_clients and requires partner scope, and that plan/billingPeriod are rejected in client mode. The enumerated `market` and `businessProfile` keys largely restate the schema.

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?

The opening clause names a specific verb and resource — "registers the domain under the caller's account" — and immediately distinguishes it from siblings by labeling it "Step 2 of adding a site," with analyze_new_site supplying inputs and complete_site_setup as the follow-up.

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

Usage Guidelines5/5

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

Explicit sequencing (values "usually from analyze_new_site, edited as needed"; "Then call complete_site_setup"), plus scoped alternatives: clientId only for white-label partners on partner-scoped credentials, plan/billingPeriod only for direct customers and refused otherwise. The 409 condition tells the agent when this call is the wrong one.

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

All Blawgy toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources