Retrieve Netlify team details, list all teams, or fetch environment variables by team ID through read-only operations.
Select and run one of the following Netlify read operations (read-only) get-teams, get-team, get-team-env-vars
| Name | Required | Description | Default |
|---|---|---|---|
| selectSchema | Yes |
Changes observed during successful MCP inspections.
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": "get-teams",
- "type": "string"
- },
- "params": {
- "additionalProperties": false,
- "properties": {},
- "type": "object"
- }
- },
- "required": [
- "operation"
- ],
- "type": "object"
- },
- {
- "additionalProperties": false,
- "properties": {
- "aiAgentName": {
- "type": "string"
- },
- "llmModelName": {
- "type": "string"
- },
- "operation": {
- "const": "get-team",
- "type": "string"
- },
- "params": {
- "additionalProperties": false,
- "properties": {
- "teamId": {
- "type": "string"
- }
- },
- "required": [
- "teamId"
- ],
- "type": "object"
- }
- },
- "required": [
- "operation"
- ],
- "type": "object"
- }
-]New value: +[
+ {
+ "properties": {
+ "aiAgentName": {
+ "type": "string"
+ },
+ "llmModelName": {
+ "type": "string"
+ },
+ "operation": {
+ "const": "get-teams",
+ "type": "string"
+ },
+ "params": {
+ "properties": {},
+ "type": "object"
+ }
+ },
+ "required": [
+ "operation"
+ ],
+ "type": "object"
+ },
+ {
+ "properties": {
+ "aiAgentName": {
+ "type": "string"
+ },
+ "llmModelName": {
+ "type": "string"
+ },
+ "operation": {
+ "const": "get-team",
+ "type": "string"
+ },
+ "params": {
+ "properties": {
+ "teamId": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "teamId"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "operation"
+ ],
+ "type": "object"
+ },
+ {
+ "properties": {
+ "aiAgentName": {
+ "type": "string"
+ },
+ "llmModelName": {
+ "type": "string"
+ },
+ "operation": {
+ "const": "get-team-env-vars",
+ "type": "string"
+ },
+ "params": {
+ "properties": {
+ "envVarKey": {
+ "type": "string"
+ },
+ "teamId": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "teamId"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "operation"
+ ],
+ "type": "object"
+ }
+]v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds the dispatcher behavior ('Select and run') beyond the readOnlyHint annotation, which is valuable. It also lists the exact operations, confirming no side effects. No contradiction with the annotation; it reinforces the read-only nature.
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?
A single, front-loaded sentence that immediately conveys the tool's purpose and enumerates the options. No wasted words; the structure is efficient and scannable.
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?
The tool is a dispatcher with three sub-operations, yet the description does not explain how to choose among them or what parameters each requires. There is no output schema, so the description should at least hint at the return format or differences. This leaves the agent under-informed for correct invocation, especially for parameter-heavy operations like get-team-env-vars.
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?
The description gives zero parameter information. With schema coverage at 0%, the description carries the full burden for explaining what each operation requires, but it only lists operation names. The agent is left to deduce that get-team needs a teamId and get-team-env-vars needs teamId and envVarKey from the schema structure, which lacks any textual guidance. This is a significant gap.
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 a clear verb ('Select and run') and a specific resource ('Netlify read operations'), and enumerates the three sub-operations. The domain (team) is evident from the tool name and the operation list, distinguishing it from the user, deploy, project, and extension sibling tools.
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?
It explicitly marks the tool as read-only, which helps avoid confusion with updater siblings. However, it does not provide guidance on when to choose this tool over other readers (e.g., user, project) nor how to select among the three sub-operations. The decision is left to the agent's inference from the operation names and schema.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.