Skip to main content
Glama
delimit-ai

delimit

Official
by delimit-ai
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

delimit_deploy_npm

Publishes an npm package: bumps version, packs, and pushes to registry. Requires prior security audit, smoke test, changelog, and deploy plan approval before production deployment.

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_pathNoPath to the npm project root. Default "." (cwd)..
bumpNoSemver bump — "patch" (default), "minor", or "major".patch
tagNonpm dist-tag for the publish. Default "latest".latest
dry_runNoIf True, run the chain without publishing. Default False.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.6/5.0
Behavior5/5

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

No annotations provided, so description fully addresses behavior: license check, local version bump, prepublishOnly hook, pack, network publish, irreversibility, and dry_run effects. Mentions a known regression.

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?

Well-structured with headings and bullet points, front-loaded purpose, and minimal redundancy. Slightly long but each sentence adds value.

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?

Given complexity (4 params, output schema present, no annotations), description thoroughly covers all aspects: purpose, usage guidelines, behavioral side effects, parameter effects, and output context.

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% with descriptions, so baseline is 3. Description adds context about dry_run suppressing only publish step, but does not significantly extend beyond schema.

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?

Clearly states 'Publish an npm package: version bump, pack, and push to registry' with specific verb and resource. Distinguishes from siblings like delimit_deploy_site and delimit_deploy_publish.

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?

Explicitly defines when to use (ship new npm package version), when not to use (deploy site, push containers, dry-run locally), and provides alternatives. Also specifies prerequisite chain and founder approval requirement.

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