Retrieve Netlify deploy information using deploy ID or site and deploy ID. Enables checking deploy status and metadata without modifications.
Select and run one of the following Netlify read operations (read-only) get-deploy, get-deploy-for-site
| Name | Required | Description | Default |
|---|---|---|---|
| selectSchema | Yes |
Changes observed during successful MCP inspections.
v1.0.1Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Input schema / additionalPropertiesRemoved value: -falseInput schema / properties / selectSchema / anyOfPrevious value: -[
- {
- "additionalProperties": false,
- "properties": {
- "aiAgentName": {
- "type": "string"
- },
- "llmModelName": {
- "type": "string"
- },
- "operation": {
- "const": "get-deploy",
- "type": "string"
- },
- "params": {
- "additionalProperties": false,
- "properties": {
- "deployId": {
- "type": "string"
- }
- },
- "required": [
- "deployId"
- ],
- "type": "object"
- }
- },
- "required": [
- "operation"
- ],
- "type": "object"
- },
- {
- "additionalProperties": false,
- "properties": {
- "aiAgentName": {
- "type": "string"
- },
- "llmModelName": {
- "type": "string"
- },
- "operation": {
- "const": "get-deploy-for-site",
- "type": "string"
- },
- "params": {
- "additionalProperties": false,
- "properties": {
- "deployId": {
- "type": "string"
- },
- "siteId": {
- "type": "string"
- }
- },
- "required": [
- "siteId",
- "deployId"
- ],
- "type": "object"
- }
- },
- "required": [
- "operation"
- ],
- "type": "object"
- }
-]New value: +[
+ {
+ "properties": {
+ "aiAgentName": {
+ "type": "string"
+ },
+ "llmModelName": {
+ "type": "string"
+ },
+ "operation": {
+ "const": "get-deploy",
+ "type": "string"
+ },
+ "params": {
+ "properties": {
+ "deployId": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "deployId"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "operation"
+ ],
+ "type": "object"
+ },
+ {
+ "properties": {
+ "aiAgentName": {
+ "type": "string"
+ },
+ "llmModelName": {
+ "type": "string"
+ },
+ "operation": {
+ "const": "get-deploy-for-site",
+ "type": "string"
+ },
+ "params": {
+ "properties": {
+ "deployId": {
+ "type": "string"
+ },
+ "siteId": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "siteId",
+ "deployId"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "operation"
+ ],
+ "type": "object"
+ }
+]v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotation already declares readOnlyHint=true, and the description reinforces this by saying 'read-only', so there is no contradiction. The description adds the dispatch-like behavior of selecting between the two named operations. However, it does not disclose return format, error behavior, authentication needs, or any other behavioral traits beyond the annotation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single efficient sentence with no filler, and the core action and operation names are front-loaded. It could be slightly better structured by separating the operation list, but overall it is appropriately sized for a short tool description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with two distinct operations, nested parameters, and no output schema, this description is incomplete. It lacks parameter guidance, decision criteria between operations, and any indication of what the operations return. The read-only safety is covered, but essential calling context is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description carries full responsibility for explaining parameters. It only lists operation names without mentioning deployId, siteId, or how the selectSchema discriminator works. The schema itself provides no descriptions either, leaving an agent without meaningful parameter semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific action ('Select and run') applied to Netlify read operations and names the two supported operations, get-deploy and get-deploy-for-site. It clearly identifies this as a read-only tool, which distinguishes it from sibling updater tools at a basic level. It stops short of describing what each operation returns, so it is not fully self-contained.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives a general context: run one of the listed Netlify read operations. It does not explain when to choose get-deploy versus get-deploy-for-site, nor does it explicitly contrast this tool with sibling readers or updaters. An agent is left to infer selection criteria from operation names alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.