Skip to main content
Glama
delimit-ai

delimit

Official
by delimit-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Delimit Deploy Npm

delimit_deploy_npm

Publish an npm package to the registry: bump version, pack, and push after passing security, test, and changelog gates. Use dry_run to validate the chain without a live publish.

Instructions

Publish an npm package: version bump, pack, and push to registry (Pro).

When to use: to ship a new version of an npm-published package (delimit-cli, a venture SDK, etc.). This is a PRODUCTION DEPLOY — every successful publish reaches real users, so it must be preceded by the deploy gate chain (delimit_security_audit -> delimit_test_smoke -> delimit_changelog -> delimit_deploy_plan) and by package acceptance against the PACKED candidate in a clean room. Publication itself is DELEGATED under the owner amendment of 2026-09-19 ("Delegated Merges and Batched npm Releases") — it no longer waits on a founder click — but the gate chain is fully binding and a failed gate is a HOLD. When NOT to use: to deploy a site (use delimit_deploy_site), to push container images (delimit_deploy_publish), to dry-run locally (npm pack --dry-run is faster), or to test the chain without publishing — for that, pass dry_run=True here.

Sibling contrast: delimit_deploy_site ships UI / static; this ships npm tarballs to the registry. Compared to running npm publish by hand, this wraps the chain with a bump, governance gate, and is the auditable surface that other tools can chain against.

Side effects: gated by require_premium — unlicensed callers receive a license payload and no publish runs. On a licensed call, invokes backends.tools_infra.deploy_npm which runs the npm publish chain: (1) bumps the version in package.json (LOCAL write to the source tree), (2) runs the project's prepublishOnly hook if present (which may build or sync artifacts — note the 2026-05-08 v4.5.12 prepublish regression), (3) runs npm pack and (4) npm publish to the configured registry — a NETWORK write that is publicly visible and NOT undoable except by an unpublish (heavily restricted by npm). dry_run=True suppresses step (4) only — the version bump and pack still happen so the chain can be exercised.

Prerequisite: requires Delimit Pro. An unlicensed call returns {"error": ..., "upgrade": "https://delimit.ai/pricing"} without running.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNonpm dist-tag for the publish. Default "latest".latest
bumpNoSemver bump — "patch" (default), "minor", or "major".patch
dry_runNoIf True, run the chain without publishing. Default False.
repo_pathNoRequired explicit Git worktree/package root; never derived from cwd.
project_pathNoDeprecated compatibility field; repo_path is authoritative..

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv4.13.2
    • changedInput schema / properties / project_path / description
      Previous value: -"Path to the npm project root. Default \".\" (cwd)."New value: +"Deprecated compatibility field; repo_path is authoritative."
    • addedInput schema / properties / repo_path
      Added value: +{
+  "default": "",
+  "description": "Required explicit Git worktree/package root; never derived from cwd.",
+  "type": "string"
+}
  2. Changed4 schema fields changedv4.7.9
    • addedInput schema / properties / bump / description
      Added value: +"Semver bump — \"patch\" (default), \"minor\", or \"major\"."
    • addedInput schema / properties / dry_run / description
      Added value: +"If True, run the chain without publishing. Default False."
    • addedInput schema / properties / project_path / description
      Added value: +"Path to the npm project root. Default \".\" (cwd)."
    • addedInput schema / properties / tag / description
      Added value: +"npm dist-tag for the publish. Default \"latest\"."
  3. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

The description goes well beyond the annotations by enumerating the exact four-step chain, labeling the local package.json write and the irreversible network publish, and warning about the prepublishOnly hook. It also discloses license-gating behavior and dry_run's precise effect (suppresses step 4 only). This is not contradicted by destructiveHint=false because the operation is additive rather than deleting existing data, and readOnlyHint=false already signals a mutating call.

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?

The description is clearly sectioned and front-loads the core action and risk. It is longer than strictly necessary, with governance-amendment and historical regression details that are not needed to invoke the tool, but the structure keeps those as asides rather than burying the essential information.

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 production-deploy tool with five parameters, the description covers licensing, prerequisite gate chain, exact side effects, dry-run behavior, and explicit alternatives. Since an output schema exists, omitting return-value details is acceptable, and nothing an agent needs to decide whether and how to call it is missing.

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 the description need not re-document every parameter. It adds useful nuances for dry_run and for repo_path's 'never derived from cwd' rule, but it also calls repo_path 'Required' while the schema lists no required parameters and gives it a default—an inconsistency that could confuse an agent deciding whether it may omit the field.

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?

Opening sentence names the exact resource and action: 'Publish an npm package: version bump, pack, and push to registry'. The sibling-contrast paragraph explicitly distinguishes it from delimit_deploy_site and delimit_deploy_publish, so an agent can tell it apart from nearby deploy tools without inspecting their schemas.

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?

Includes explicit 'When to use' and 'When NOT to use' sections with concrete alternative tool names (delimit_deploy_site, delimit_deploy_publish) and alternative workflows (`npm pack --dry-run`, dry_run=True). It also states the binding prerequisite gate chain, so an agent knows the call must be preceded by security audit, smoke test, changelog, and plan.

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