Skip to main content
Glama

deploy_function

Deploy a serverless Node 22 function to a project with automatic bundling of npm dependencies and optional cron scheduling.

Instructions

Deploy a serverless function (Node 22) to a project. Handler signature: export default async (req: Request) => Response. The function can import { db, adminDb, auth, email, ai } from '@run402/functions' — auto-bundled by the platform. Additional npm packages are bundled at deploy time when listed in deps (bare names resolve to latest; pinned/range specs are honored verbatim; @run402/functions and run402-functions rejected; max 30 entries; native binaries rejected). The response includes runtime_version (the bundled @run402/functions version — surface as 'Functions runtime version', never bare 'runtime'), deps_resolved (map of dep name → installed concrete version), and an optional top-level warnings array (sibling to the function record).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesTypeScript or JavaScript source code. Must export a default async function: export default async (req: Request) => Response
depsNoOptional npm package specs to install and bundle. Bare names (e.g. 'lodash') resolve to latest at deploy time; pinned (e.g. 'lodash@4.17.21') or range specs ('date-fns@^3.0.0') are honored verbatim. '@run402/functions' (auto-bundled) and 'run402-functions' (legacy name) are rejected. Max 30 entries, max 200 chars per spec. Native binary modules (sharp, canvas, native bcrypt, etc.) are rejected.
nameYesFunction name (URL-safe slug: lowercase, hyphens, alphanumeric, e.g. 'stripe-webhook')
configNoOptional function configuration
scheduleNoCron expression (5-field, e.g. '*/15 * * * *') to run the function on a schedule. Pass null to remove an existing schedule.
project_idYesThe project ID to deploy the function to
Behavior4/5

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

No annotations, so description carries full burden. Discloses auto-bundling behavior, NPM dependency resolution, rejection rules, and response structure (runtime_version, deps_resolved, warnings). Lacks mention of destructive implications or auth requirements, but deployment is inherently safe.

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?

Single paragraph but well-structured: starts with main purpose, then detailed rules. Every sentence adds value. Could be slightly more scannable with bullet points, but efficient for the complexity.

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?

Given 6 params, 3 required, nested config object, and no output schema, the description covers function behavior, dependency rules, response fields, and schedule format. Lacks explicit error handling or rate limits, but overall thorough for a deploy tool.

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

Parameters5/5

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

Schema coverage is 100%, baseline 3. Description adds significant value: explains handler signature for 'code', dependency rules for 'deps', slug constraints for 'name', memory/timeout defaults, cron format for 'schedule'. Goes well beyond schema descriptions.

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 the action (deploy), resource (serverless function with Node 22 runtime), and target (project). Distinguishes from sibling tools like delete_function, update_function, invoke_function by specifying handler signature and auto-bundled imports.

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?

Provides extensive usage guidance: handler signature, allowed imports, dependency rules (bare names vs pinned, max 30 entries, rejected packages), schedule expression format. Implicitly tells when to use (deploy new function) but doesn't explicitly differentiate from update_function.

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/kychee-com/run402-mcp'

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