Skip to main content
Glama
Sign In
multi-account-netlify-mcp

multi-account-netlify-mcp

by FiredMosquito831
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

netlify-deploy-services-reader

Read-onlyIdempotent

Read a Netlify deploy by deploy ID, or by site and deploy ID, across one, several, or all accounts; returns the owning account and lists accounts where it is not found.

Instructions

Select and run one of the following Netlify read operations (read-only) get-deploy, get-deploy-for-site

Multi-account (the account argument): get-deploy: only the account that owns the id answers, and accounts without it are listed under notFoundIn; get-deploy-for-site: 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-deploy-services-reader"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoNetlify 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.
selectSchemaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, openWorld and non-destructive, so the bar is lower; the description still adds real behavioral context that annotations cannot express — only the owning account answers for a given id, and non-owning accounts are surfaced under notFoundIn. That multi-account resolution detail is genuinely useful for interpreting results.

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 leading sentence is front-loaded and useful, but the multi-account paragraph repeats the identical clause verbatim for both operations ('only the account that owns the id answers, and accounts without it are listed under notFoundIn'), bloating the definition 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 read-only tool with two parameters and no output schema, the description covers operation selection and account behavior but says nothing about what a deploy record contains or how results are shaped. Adequate but leaves the agent to discover return content on its own.

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 description coverage is 50%; the account property is documented in-schema and the description reinforces its multi-account semantics ('one name, several names separated by commas, or "all"' is schema-side). The nested params (deployId, siteId) carry no prose in either place, so the description only partially compensates.

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?

Names a specific resource (Netlify deploy read operations) and enumerates the two selectable operations, get-deploy and get-deploy-for-site. A reader can tell this apart from the sibling netlify-deploy-services-updater by the '(read-only)' qualifier, though the two operations' own distinction is left for the schema to reveal.

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?

Usage is implied by 'Select and run one of the following Netlify read operations' and the account-scoping paragraph, but there is no explicit statement of when to pick get-deploy versus get-deploy-for-site, nor any exclusion against the updater sibling. The agent must infer operation choice from the required params.

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