timeweb-mcp-server

timeweb_create_app

Deploy a GitHub repository as a PaaS app by supplying name, type, resource preset, and repository ID. Optionally define environment variables, build/run commands, and branch.

Instructions

Create a new PaaS application from GitHub repository

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": {
      "name": "<name>",
      "type": "<type>",
      "preset_id": "<preset_id>",
      "repository_id": "<repository_id>"
    },
    "name": "timeweb_create_app"
  }
}

Input Schema

Name	Required	Description
`envs`	No	Environment variables as key-value pairs
`name`	Yes	Application name
`type`	Yes	Application type
`branch`	No	Git branch to deploy (default: main)
`format`	No	Output format: 'markdown' for human-readable or 'json' for machine-readable
`preset_id`	Yes	Preset ID for resources
`run_command`	No	Run command (e.g., 'npm start')
`build_command`	No	Build command (e.g., 'npm run build')
`repository_id`	Yes	GitHub repository ID (from connected account)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It states the core action and source but omits any side effects (e.g., resource provisioning, potential costs), required prior setup (GitHub connection), or how the created app is identified. It adds minimal context beyond the functional summary.

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?

The description is a single sentence, front-loaded with the verb and object, and contains no redundant or ambiguous wording. It is maximally concise and easy to parse.

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

Completeness2/5

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

Despite the detailed input schema, there is no output schema and no annotations. The description does not explain return values, post-creation steps, or operational caveats. For a create operation with 9 parameters, this is insufficient for an agent to understand the full lifecycle.

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?

The input schema already provides detailed descriptions for all 9 parameters, including enums and defaults, achieving 100% coverage. The description adds no additional parameter-level information, so it neither improves nor detracts from the schema's clarity, meeting the baseline.

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 description clearly states the action ('Create'), the resource ('PaaS application'), and the specific source ('from GitHub repository'). This differentiates it from sibling create tools like create_server or create_database, and from app management tools like update_app or delete_app.

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 offers no guidance on when to use this tool, prerequisites (e.g., needing a connected GitHub account), or exclusion cases. It does not mention any alternatives or preferred contexts beyond the literal action.

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

Deploy Server