shiply

Set or update a cron trigger

set_cron

Idempotent

Set or update a cron trigger on a site's deployed function. Schedule is crontab syntax (UTC). Path is the URL the cron handler should fire on (for the worker's scheduled() handler context).

Input Schema

TableJSON Schema

Name	Required	Description
`path`	Yes	URL path the cron handler fires on
`slug`	Yes	site slug whose function gets the cron
`schedule`	Yes	crontab schedule in UTC, e.g. "0 * * * *"

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.

Changed4 schema fields changedJun 23, 2026

addedInput schema / properties / path / description

Added value: +"URL path the cron handler fires on"

addedInput schema / properties / schedule / description

Added value: +"crontab schedule in UTC, e.g. \"0 * * * *\""

addedInput schema / properties / slug / description

Added value: +"site slug whose function gets the cron"

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?

Annotations provide idempotentHint=true, but description adds behavioral context about crontab syntax and path for the worker's scheduled handler. However, it omits details about update behavior, validation, or error conditions.

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?

Two concise sentences with front-loaded purpose. Every sentence adds value without redundancy.

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 presence of an output schema, the description does not need to explain return values. It provides sufficient context for the simple set/update operation, though more details on side effects could be added.

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?

Schema coverage is 100% with parameter descriptions. Description adds extra context beyond schema, clarifying that the path is for the worker's scheduled() handler and that schedule uses UTC crontab syntax.

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?

Description clearly states verb 'Set or update' and resource 'cron trigger on a site's deployed function'. It specifies the schedule format and path purpose, distinguishing from sibling tools like list_crons and remove_cron.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description implicitly indicates usage for creating/updating crons, but does not explicitly state when to use versus alternatives like remove_cron or list_crons. No when-not guidance is provided.

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?