Skip to main content
Glama
delimit-ai

delimit

Official
by delimit-ai
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

Delimit Deploy Npm

delimit_deploy_npm

Publish a new npm package version by bumping semver, packing, and pushing to the registry after required deploy gates, with dry-run support.

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 explicit founder approval per the customer-protection rule. 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. Dates show when Glama detected each change.

  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.9/5.0
Behavior5/5

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

Beyond readOnlyHint=false, the description discloses step-by-step side effects: local package.json bump, prepublishOnly hook execution (including a known regression), npm pack, and npm publish as a publicly visible network write that is not undoable. It also covers dry_run's exact scope (suppresses step 4 only) and the unlicensed-caller behavior, giving the agent a precise model of consequences. This does not contradict destructiveHint=false because publishing is not deleting data, but it correctly labels the side effect as irreversible.

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 long but every paragraph earns its place: purpose, routing guidance, sibling contrast, side effects, and prerequisites are each one dense block with no filler. It front-loads the core action and immediately follows with deployment-safety context.

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, the description fully covers what will happen, what won't happen in dry run, what must precede it, who can call it, and which sibling tools handle other cases. The output schema exists, so return-value documentation is not the description's job; nothing needed for correct invocation is missing.

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

Parameters4/5

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

Input schema already covers all five parameters (100%), so baseline is 3; the description earns extra by adding one important behavioral nuance: dry_run=True still performs the version bump and pack, not just a no-op, so the chain can be exercised. It also clarifies that this is a Pro-gated operation, which indirectly prepares the agent for a license-related response. No per-parameter details beyond what the schema already provides are added, so 4 rather than 5.

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 opens with a precise action and resource: 'Publish an npm package: version bump, pack, and push to registry (Pro).' It distinguishes itself from delimit_deploy_site and delimit_deploy_publish by naming exactly what it ships (npm tarballs) versus sites or container images, so an agent can disambiguate immediately.

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?

The 'When to use' and 'When NOT to use' sections are explicit, naming the correct alternative for each excluded case (delimit_deploy_site, delimit_deploy_publish, local npm pack --dry-run) and even pointing to dry_run=True for testing the chain without publishing. It also states the required preceding chain and founder approval, leaving no ambiguity about when invoking it is appropriate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/delimit-ai/delimit-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server