multi-account-netlify-mcp

netlify-extension-services-reader

Read-onlyIdempotent

Read Netlify extension data across accounts by selecting a read-only operation: list extensions, fetch full details by team and slug, or initialize the database.

Instructions

Select and run one of the following Netlify read operations (read-only) get-extensions, get-full-extension-details, initialize-database

Multi-account (the account argument): get-extensions: every named account answers; get-full-extension-details: only the account that owns the id answers, and accounts without it are listed under notFoundIn; initialize-database: every named account answers.

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-extension-services-reader"
  }
}

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

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so safety is covered. The description adds genuinely new behavioral detail: which operations answer for every named account versus only the owning account, and that non-owning accounts surface under notFoundIn. This multi-account semantics is not in the annotations or schema.

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?

Front-loaded with the purpose and operation list, then the multi-account detail. Dense but no wasted sentences; the operation list could have been formatted more scannably but the content earns its place.

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 two-parameter dispatcher with no output schema, the definition covers account semantics well but never explains what each operation does or returns, leaving an agent unable to confidently pick between get-extensions, get-full-extension-details, and initialize-database.

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 coverage is only 50%, and the description compensates by explaining the account argument's effect per operation, which the schema does not detail. It does not, however, add meaning for the extensionSlug/teamId params of get-full-extension-details beyond what the schema already says.

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 names a clear verb+resource ('run ... Netlify read operations') and enumerates the three selectable operations, while the read-only framing separates it from the sibling netlify-extension-services-updater. It does not explain what each operation actually returns, so the distinction between get-extensions and get-full-extension-details remains opaque.

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?

'Select and run one of the following' implies usage but gives no condition for choosing one operation over another, and no guidance on when this reader is preferred over the sibling updater. The per-operation account behavior is useful context but is about execution mechanics, not when-to-use.

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

Deploy Server