Skip to main content
Glama
tasklite-net

TaskLite MCP

by tasklite-net
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

rollback_deployment

Revert your live app to a previous deployment version using the app ID and version number. Fix issues introduced by the current release without changing the live URL.

Instructions

Point the live URL back at a previous deployment version (see list_deployments for available versions).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdYesApp id or slug (from list_apps / create_app)
versionYesDeployment version number (from list_deployments)
organizationIdNoOrganization id; defaults to the credential organization when omitted

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.13.0
    • addedInput schema / properties / appId / description
      Added value: +"App id or slug (from list_apps / create_app)"
    • addedInput schema / properties / organizationId / description
      Added value: +"Organization id; defaults to the credential organization when omitted"
    • addedInput schema / properties / version / description
      Added value: +"Deployment version number (from list_deployments)"
  2. First observedv0.7.0

TDQS

A3.8/5.0
Behavior2/5

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

The description does not disclose that this action overwrites the current live deployment, nor does it mention whether the change is reversible, the required permissions, or any confirmation step. The destructiveHint annotation is false, but the action has a significant impact on the live environment, so transparency is lacking.

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, direct sentence with no fluff. It efficiently conveys the purpose and points to a related tool, making it concise and well-structured.

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?

The description is adequate for the operation's simplicity, but it omits details about the return value or success/failure indicators. Given that no output schema is provided, this is a minor gap and does not hinder basic usage.

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 schema descriptions already cover appId and version thoroughly, and the description adds minimal extra meaning (e.g., 'previous deployment version'). Since the schema coverage is 100%, the description does not need to compensate, but it also does not enrich the parameters further.

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 ('Point the live URL back') and the target resource ('a previous deployment version'), and references list_deployments for available versions, distinguishing it from sibling tools like deploy_frontend or list_deployments.

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?

It implicitly guides usage by referencing list_deployments to find versions, but does not explicitly contrast with deploy_frontend or state conditions for when a rollback is preferred over a new deployment. Still, the context is clear enough for an agent.

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