multi-account-netlify-mcp

netlify-project-services-updater

Destructive

Update Netlify project services such as visitor access controls, forms, submissions, names, and environment variables, or create a new project using a chosen account.

Instructions

Select and run one of the following Netlify write operations update-visitor-access-controls, update-forms, manage-form-submissions, update-project-name, manage-env-vars, create-new-project

Multi-account (the account argument): update-visitor-access-controls: one account only, so a list or all is refused; update-forms: one account only, so a list or all is refused; manage-form-submissions: get-submissions needs the account that owns the form (only it answers); delete-submission needs one account; update-project-name: one account only, so a list or all is refused; manage-env-vars: listing needs the account that owns the site (only it answers); creating, updating and deleting need one account; create-new-project: one account only, so a list or all is refused.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "selectSchema": "<selectSchema>"
    },
    "name": "netlify-project-services-updater"
  }
}

Input Schema

Name	Required	Description	Default
`account`	No	Netlify account to use: one name, several names separated by commas, or "all". Lists and all only work for operations that allow them; changes need one name. Leave out to use the default account. Accounts: none yet.
`selectSchema`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.3Oct 19, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered. The description adds value by disclosing account-scoping behavior per operation ('only it answers', 'a list or all is refused'), but says nothing about permissiveness requirements, reversibility of the six mutations, or side effects, which a destructive dispatcher should ideally cover.

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 operation list is helpfully front-loaded, but the second half is a long run-on paragraph that repeats the identical phrase 'one account only, so a list or all is refused' four times instead of grouping the operations that share the constraint. The repeated boilerplate costs space without adding information.

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?

For a six-operation dispatcher with a discriminated union schema and no output schema, the description covers only the account dimension and never explains what the individual operations actually do (e.g., what update-visitor-access-controls or update-forms change). Operation names are reasonably self-descriptive and params live in the schema, but the write semantics an agent needs before committing are largely absent.

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 description coverage is 50% and the selectSchema union carries no description at all, so the description must compensate. It does so meaningfully for the account parameter by spelling out exactly which of the six operations tolerate a single name, a comma list, or 'all' — detail the schema's own account description only gestures at.

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

Purpose4/5

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

The description states a specific verb and resource: 'Select and run one of the following Netlify write operations', then names all six operations. The word 'write' implicitly separates it from the netlify-project-services-reader sibling, though it never names that sibling or distinguishes itself from netlify-deploy-services-updater, which also performs writes.

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 guidance given is almost entirely about the account argument for each operation (which operations accept lists/all vs. a single account), which is real routing advice but scoped to one parameter. There is no explicit statement of when to pick this tool over the reader sibling or the deploy updater, so tool-level selection is left to inference.

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

Deploy Server