Read Netlify project details, list projects, or fetch forms for a project using read-only operations.
Select and run one of the following Netlify read operations (read-only) get-project, get-projects, get-forms-for-project
| 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-project",
- "type": "string"
- },
- "params": {
- "additionalProperties": false,
- "properties": {
- "siteId": {
- "type": "string"
- }
- },
- "required": [
- "siteId"
- ],
- "type": "object"
- }
- },
- "required": [
- "operation"
- ],
- "type": "object"
- },
- {
- "additionalProperties": false,
- "properties": {
- "aiAgentName": {
- "type": "string"
- },
- "llmModelName": {
- "type": "string"
- },
- "operation": {
- "const": "get-projects",
- "type": "string"
- },
- "params": {
- "additionalProperties": false,
- "properties": {
- "projectNameSearchValue": {
- "description": "Search for a project by partial name match",
- "type": "string"
- },
- "teamSlug": {
- "type": "string"
- }
- },
- "type": "object"
- }
- },
- "required": [
- "operation"
- ],
- "type": "object"
- },
- {
- "additionalProperties": false,
- "properties": {
- "aiAgentName": {
- "type": "string"
- },
- "llmModelName": {
- "type": "string"
- },
- "operation": {
- "const": "get-forms-for-project",
- "type": "string"
- },
- "params": {
- "additionalProperties": false,
- "properties": {
- "formId": {
- "type": "string"
- },
- "siteId": {
- "type": "string"
- }
- },
- "required": [
- "siteId"
- ],
- "type": "object"
- }
- },
- "required": [
- "operation"
- ],
- "type": "object"
- }
-]New value: +[
+ {
+ "properties": {
+ "aiAgentName": {
+ "type": "string"
+ },
+ "llmModelName": {
+ "type": "string"
+ },
+ "operation": {
+ "const": "get-project",
+ "type": "string"
+ },
+ "params": {
+ "properties": {
+ "siteId": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "siteId"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "operation"
+ ],
+ "type": "object"
+ },
+ {
+ "properties": {
+ "aiAgentName": {
+ "type": "string"
+ },
+ "llmModelName": {
+ "type": "string"
+ },
+ "operation": {
+ "const": "get-projects",
+ "type": "string"
+ },
+ "params": {
+ "properties": {
+ "projectNameSearchValue": {
+ "description": "Search for a project by partial name match",
+ "type": "string"
+ },
+ "teamSlug": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ }
+ },
+ "required": [
+ "operation"
+ ],
+ "type": "object"
+ },
+ {
+ "properties": {
+ "aiAgentName": {
+ "type": "string"
+ },
+ "llmModelName": {
+ "type": "string"
+ },
+ "operation": {
+ "const": "get-forms-for-project",
+ "type": "string"
+ },
+ "params": {
+ "properties": {
+ "formId": {
+ "type": "string"
+ },
+ "siteId": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "siteId"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "operation"
+ ],
+ "type": "object"
+ }
+]v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description's only behavioral content - '(read-only)' - merely repeats readOnlyHint=true and adds nothing about response shape, pagination, or auth requirements. No contradiction, but no value added.
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 with no waste; the operation list is placed where an agent needs it. It is arguably too terse given the schema complexity, but there is no filler.
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?
For a three-way dispatch tool with a nested anyOf schema, 0% param coverage, and no output schema, the description is far too thin. It neither explains the operations' semantics nor the parameters, so an agent cannot confidently construct a call from the description alone.
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?
Schema description coverage is 0%, so the description must compensate for undocumented params like siteId, teamSlug, formId, and projectNameSearchValue. Instead it only names the operations and provides no parameter meaning, leaving the nested anyOf schema to speak for itself.
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?
States a specific verb and resource - it is a dispatcher that selects and runs one of three named Netlify project read operations - and the '(read-only)' phrasing distinguishes it from the netlify-project-services-updater sibling. It stops short of saying what each individual operation returns, so an agent still has to infer the meaning of get-forms-for-project.
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?
There is no guidance on when to pick get-project versus get-projects versus get-forms-for-project, nor any mention of the updater sibling as the write alternative. The user is left to infer selection purely from the operation names.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.