shiply

Deploy a Worker function to a site

deploy_function

Idempotent

Deploy a Worker function to a site. The function runs on every request to .shiply.now and can receive webhooks, run on cron triggers, and access bindings (D1, secrets, env vars). Requires Developer plan. Use when the user wants webhook receivers, cron jobs, or a backend for their site.

Input Schema

TableJSON Schema

Name	Required	Description
`lang`	No	source language (default js)
`slug`	Yes	site slug to deploy the function to
`crons`	No	cron triggers to register, ≤20
`source`	Yes	the Worker source code

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed7 schema fields changedJun 23, 2026

addedInput schema / properties / crons / description
```
Added value: +"cron triggers to register, ≤20"
```
addedInput schema / properties / crons / items / properties / path / description
```
Added value: +"URL path the cron handler fires on"
```
addedInput schema / properties / crons / items / properties / schedule / description
```
Added value: +"crontab schedule in UTC, e.g. \"0 * * * *\""
```
addedInput schema / properties / lang / description
```
Added value: +"source language (default js)"
```

addedInput schema / properties / slug / description

Added value: +"site slug to deploy the function to"

addedInput schema / properties / source / description
```
Added value: +"the Worker source code"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "result": {}
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}

First observedJun 23, 2026

TDQS

A4/5.0

Behavior3/5

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

The description discloses that the function runs on every request, supports webhooks and crons, and requires a Developer plan. Annotations only provide idempotentHint; the description adds value but lacks details on conflict behavior (e.g., overwriting existing functions) or any side effects beyond deployment.

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 very concise: two sentences plus a usage line, all front-loaded. Every word adds value with no repetition or fluff.

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 the tool's complexity, the description covers the main purpose, capabilities, and usage context. It does not mention prerequisites like the site needing to exist (though implied by the required slug). An output schema exists, so return value details are not needed. Overall adequate.

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 each parameter is already described. The description adds overarching context (function capabilities) but does not provide additional meaning to individual parameters beyond the schema. Baseline 3 is appropriate.

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 it deploys a Worker function to a site, specifying the target URL pattern and capabilities like webhooks, cron triggers, and bindings. It distinguishes from siblings like publish_site (static sites) and set_cron (managing crons on existing functions).

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?

Explicitly says 'Use when the user wants webhook receivers, cron jobs, or a backend for their site.' and mentions 'Requires Developer plan.' This provides clear context for when to use, though it does not explicitly mention when not to use or alternatives.

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

All shiply tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0

Disambiguation2/5

Many tools have overlapping purposes (e.g., add_domain, add_subdomain, add_custom_domain, add_sending_domain) or similar names like check_domain and check_custom_domain, which can confuse an agent. While descriptions help, the sheer number of closely related tools makes it difficult to consistently select the correct one.

Naming Consistency3/5

Most tools follow a verb_noun pattern, but there are exceptions like 'read_thread' (instead of get_thread) and 'mark_thread_read' (verb_noun_verb). Prefixes like 'data_' are used inconsistently with other tools, but overall the naming is still readable.

Tool Count1/5

With 103 tools, the server is extremely bloated. Even for a comprehensive platform, this count overwhelms any agent and makes the tool surface difficult to navigate. Many tools could be merged or are too granular.

Completeness4/5

The toolset covers a wide range of operations across sites, domains, email, marketplace, projects, contracts, and functions. While some updates (e.g., general contract editing) are missing, the surface is mostly comprehensive for the domain.

Resources

Need Help?