Skip to main content
Glama
netlify

Netlify MCP Server

Official
by netlify
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

netlify-extension-services-updater

Manage Netlify extension installations or initialize the database by selecting the write operation that matches your current task.

Instructions

Select and run one of the following Netlify write operations change-extension-installation, initialize-database

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selectSchemaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / selectSchema / anyOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "aiAgentName": {
-        "type": "string"
-      },
-      "llmModelName": {
-        "type": "string"
-      },
-      "operation": {
-        "const": "change-extension-installation",
-        "type": "string"
-      },
-      "params": {
-        "additionalProperties": false,
-        "properties": {
-          "extensionSlug": {
-            "type": "string"
-          },
-          "shouldBeInstalled": {
-            "type": "boolean"
-          },
-          "siteId": {
-            "description": "Site id of the current project site. If unsure, ask what Netlify site",
-            "type": "string"
-          },
-          "teamId": {
-            "description": "Team id of the current project team. If unsure, ask what Netlify team",
-            "type": "string"
-          }
-        },
-        "required": [
-          "extensionSlug",
-          "shouldBeInstalled",
-          "teamId"
-        ],
-        "type": "object"
-      }
-    },
-    "required": [
-      "operation"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "aiAgentName": {
-        "type": "string"
-      },
-      "llmModelName": {
-        "type": "string"
-      },
-      "operation": {
-        "const": "initialize-database",
-        "type": "string"
-      },
-      "params": {
-        "additionalProperties": false,
-        "properties": {},
-        "type": "object"
-      }
-    },
-    "required": [
-      "operation"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "properties": {
+      "aiAgentName": {
+        "type": "string"
+      },
+      "llmModelName": {
+        "type": "string"
+      },
+      "operation": {
+        "const": "change-extension-installation",
+        "type": "string"
+      },
+      "params": {
+        "properties": {
+          "extensionSlug": {
+            "type": "string"
+          },
+          "shouldBeInstalled": {
+            "type": "boolean"
+          },
+          "siteId": {
+            "description": "Site id of the current project site. If unsure, ask what Netlify site",
+            "type": "string"
+          },
+          "teamId": {
+            "description": "Team id of the current project team. If unsure, ask what Netlify team",
+            "type": "string"
+          }
+        },
+        "required": [
+          "extensionSlug",
+          "shouldBeInstalled",
+          "teamId"
+        ],
+        "type": "object"
+      }
+    },
+    "required": [
+      "operation"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "aiAgentName": {
+        "type": "string"
+      },
+      "llmModelName": {
+        "type": "string"
+      },
+      "operation": {
+        "const": "initialize-database",
+        "type": "string"
+      },
+      "params": {
+        "properties": {},
+        "type": "object"
+      }
+    },
+    "required": [
+      "operation"
+    ],
+    "type": "object"
+  }
+]
  2. Addedv1.0.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already indicate readOnlyHint=false, and the description repeats that these are write operations, adding no new behavioral context. It does not disclose side effects, required permissions, or any consequences of execution. For a write operation, the description carries minimal transparency 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise, but it is under-specified. It front-loads the action but fails to earn its place by providing meaningful detail. It is not verbose, but it is not useful either.

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

Completeness2/5

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

Given the tool's complexity (a dispatcher with two operations, one with parameters and one without), the description is severely incomplete. It does not explain the purpose of each operation, their parameters, or the selection logic. An agent cannot reliably invoke this tool without additional external knowledge. The absence of an output schema further increases the burden on the description.

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

Parameters1/5

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

Schema description coverage is 0%, so the description must compensate for parameter meaning. However, it does not mention any parameters at all. The selectSchema parameter is complex (a union with two operation variants), but the description offers no explanation of how to populate it, what the operation names mean, or how to choose between them. This is a critical gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it 'Select and run one of the following Netlify write operations', which conveys a clear action and domain (Netlify write operations). However, it does not explain what each operation actually does; it only lists names. An agent can infer some meaning from the operation names, but the description itself is vague about the tool's specific function beyond being a dispatcher.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus sibling tools like the readers or other updaters. It does not mention alternatives, prerequisites, or conditions that would select one operation over the other. The agent is left to infer usage from the operation names and schema, which is insufficient.

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

Deploy Server

Other Tools