multi-account-netlify-mcp

netlify-team-services-reader

Read-onlyIdempotent

Read Netlify team details and environment variables across one, multiple, or all accounts, with read-only operations that route each request to the correct account.

Instructions

Select and run one of the following Netlify read operations (read-only) get-teams, get-team, get-team-env-vars

Multi-account (the account argument): get-teams: every named account answers; get-team: only the account that owns the id answers, and accounts without it are listed under notFoundIn; get-team-env-vars: only the account that owns the id answers, and accounts without it are listed under notFoundIn.

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-team-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 cover readOnly/idempotent/openWorld, so the safety profile is set. The description adds genuinely new context: for get-team and get-team-env-vars only the owning account responds and non-owning accounts surface under notFoundIn, a return-behavior detail not available in the annotations.

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?

Purpose is front-loaded in the first line, and the multi-account paragraph, while slightly repetitive between get-team and get-team-env-vars, earns its place by disclosing routing behavior.

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

Completeness4/5

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

For a read-only selector tool with no output schema, the description covers operation selection and the notable multi-account result routing (notFoundIn). The main gap is that the per-operation params (teamId, envVarKey) are left unexplained.

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

Parameters3/5

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

Schema coverage is only 50%, so the description needs to compensate. It does explain the multi-account semantics of the 'account' argument well, but says nothing about teamId or envVarKey and their meaning, so coverage remains incomplete.

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 the specific operations (get-teams, get-team, get-team-env-vars) and frames the tool as a Netlify team-services reader, so the verb+resource is clear. It does not explicitly distinguish itself from sibling readers like netlify-project-services-reader, but the 'team' scope makes the domain evident.

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?

It gives selection guidance among its own sub-operations and describes multi-account behavior, which helps an agent choose. However, it never states when to use this reader versus the other netlify-*-services-reader siblings, leaving cross-tool selection 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