Install or remove a Netlify extension for a team or site by selecting the change-extension-installation operation and setting its slug and install status.
Select and run one of the following Netlify write operations change-extension-installation
| Name | Required | Description | Default |
|---|---|---|---|
| selectSchema | Yes |
Changes observed during successful MCP inspections.
v1.0.3Input schema / properties / selectSchema / anyOfRemoved 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"
- }
-]Input schema / properties / selectSchema / propertiesAdded value: +{
+ "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"
+ }
+}Input schema / properties / selectSchema / requiredAdded value: +[
+ "operation"
+]Input schema / properties / selectSchema / typeAdded value: +"object"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": "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"
+ }
+]v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=true, and openWorldHint=true. The description adds no behavioral context beyond repeating that it is a write operation—it does not describe what gets destroyed, authentication needs, or side effects.
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?
It is a single sentence, but it is poorly structured and front-loads boilerplate ('Select and run one of the following') while giving no useful detail. The phrase 'one of the following' is misleading when only a single operation is listed.
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 destructive write tool with a nested selectSchema object and no output schema, the description is far too thin. It omits what the operation does, required parameters, and any return or side-effect information.
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?
Top-level schema description coverage is 0%, and the description mentions no parameters at all. Required nested fields (extensionSlug, shouldBeInstalled, teamId) are undocumented, so the description fails to compensate for the schema's lack of descriptions.
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 it is a Netlify write operation to 'change-extension-installation', which gives a specific verb and resource. However, it is phrased with boilerplate ('Select and run one of the following') and never clarifies that it installs or uninstalls an extension, leaving the exact effect ambiguous.
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?
There is no guidance on when to use this tool versus alternatives such as netlify-extension-services-reader or other updater tools. The description only names the operation, not the context or conditions for invoking it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.