Skip to main content
Glama

Deploy app to a live URL

deploy_app
Idempotent

Deploy a completed PromptUI build to a live URL. The first deploy of each app is charged; redeploying that same app is free. If publishing needs a paid plan (a Free account, when the publish gate is on), the tool returns how to start the Build free trial instead of deploying.

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": {
      "buildId": "<buildId>"
    },
    "name": "deploy_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
buildIdYesThe buildId of a completed build
_confirmedNoSet to true only after the user has explicitly approved this exact write or credit-spending action.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / _confirmed
      Added value: +{
      +  "default": false,
      +  "description": "Set to true only after the user has explicitly approved this exact write or credit-spending action.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing that the first deploy spends credits while redeploys are free, and that the tool may return trial-start instructions instead of deploying. It does not repeat what annotations already say (idempotent, open-world), which is correct; the only gap is that it doesn't flag the explicit-approval requirement, though the schema covers that.

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 short sentences, front-loaded with the action, followed by cost and then the exception path. No filler and every sentence carries decision-relevant 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?

There is no output schema, and the description explains the non-deploying return case (trial instructions), which is the most surprising outcome. It doesn't describe the normal success payload (e.g., the live URL), leaving a small gap for an agent that needs to report results.

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 100%, so both buildId and _confirmed are documented in the schema. The description only reinforces that the build must be 'completed', adding little beyond what the parameter descriptions already state — baseline 3 is appropriate.

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 specific verb and resource ('Deploy a completed PromptUI build to a live URL'), which cleanly separates it from build_app (which produces the build) and the listing/status siblings. An agent knows exactly what outcome this produces.

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?

Establishes the precondition (a completed build), the cost model (first deploy charged, redeploy free), and the branch where publishing needs a paid plan. It does not name an explicit alternative tool for that branch, but the fallback behavior is described, so context is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources