Skip to main content
Glama
MCP Dokploy Online
by igoruam

previewDeployment-redeploy

Idempotent

Trigger a redeploy of a preview deployment by its ID, restarting the associated Dokploy environment so changes and fixes can be applied to the running preview.

Instructions

POST /previewDeployment.redeploy

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": {
      "previewDeploymentId": "<previewDeploymentId>"
    },
    "name": "previewDeployment-redeploy"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
descriptionNo
previewDeploymentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations already declare openWorldHint=true and idempotentHint=true, and the description adds no behavioral context beyond the HTTP method. It does not say whether the redeploy restarts, rebuilds, or resets the deployment, nor what happens to in-flight traffic or previous build state.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single line is short, but it is under-specified rather than concise — it conveys only routing information that the agent already has from the tool name. There is no front-loaded purpose statement to structure the rest.

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

Completeness1/5

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

For a mutation tool with no output schema and zero parameter documentation, the description is completely inadequate. An agent has nothing to rely on to decide when to call it or how to fill the optional fields correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden for three parameters (previewDeploymentId, title, description). It provides no meaning for any of them, leaving unclear whether title and description modify the deployment or annotate the redeploy.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is only "POST /previewDeployment.redeploy", which restates the tool name and HTTP verb without explaining what a redeploy actually does to the preview deployment. It does not distinguish this tool from siblings such as previewDeployment-delete or application-redeploy.

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

Usage Guidelines1/5

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

There is no guidance about when to use this tool, what prerequisites exist, or how it differs from the similarly named redeploy tools in the sibling list. The agent must infer everything from the endpoint path.

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