Skip to main content
Glama

Trigger deploy

render_create_deploy

Trigger a deploy for a Render service by providing the service ID. Optionally specify a Git commit, image URL, deploy mode, or clear build cache.

Instructions

Trigger deploy. Trigger a deploy for the service with the provided ID. Calls POST /services/{serviceId}/deploys on the Render Public API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commitIdNoThe SHA of a specific Git commit to deploy for a service. Defaults to the latest commit on the service's connected branch. Note that deploying a specific commit with this endpoint does not disable autodeploys for the service. You can toggle autodeploys for your service with the [Update service](https://api-docs.render.com/reference/update-service) endpoint or in the Render Dashboard. Not supported for cron jobs.
imageUrlNoThe URL of the image to deploy for an image-backed service. The host, repository, and image name all must match the currently configured image for the service.
serviceIdYesThe ID of the service
clearCacheNoIf `clear`, Render clears the service's build cache before deploying. This can be useful if you're experiencing issues with your build.do_not_clear
deployModeNoDeployment mode controlling build and deploy behavior. Defaults to `build_and_deploy` when not specified. **Validation:** `deploy_mode` cannot be combined with `commitId` or `imageUrl` or `clearCache`. build_and_deploy
Behavior3/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds the API call context but does not elaborate on the deploy process, potential impacts (e.g., service restart), or prerequisites beyond providing a serviceId.

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?

The description is short and front-loaded, but the first two sentences are slightly redundant ('Trigger deploy. Trigger a deploy...'). Still, it is concise with minimal waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the basic purpose and API call, but lacks broader context like when to use this tool versus sibling tools, what happens during deployment, or return value expectations (no output schema).

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?

All parameters have schema descriptions (100% coverage), so the description adds no additional semantic value beyond what is already in the 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?

The title and description clearly state the action ('Trigger deploy') and resource ('for the service with the provided ID'), including the API endpoint. It distinguishes from sibling tools like render_cancel_deploy and render_rollback_deploy.

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?

The description does not explicitly state when to use this tool versus alternatives (e.g., render_preview_service or render_run_cron_job). Usage is implied through the parameter requirements, but no comparative guidance is provided.

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/LuSrodri/render-useful-mcp'

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