Retrieve Netlify project details, list projects by partial name, or fetch forms for a specific site 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?
The description aligns with the readOnlyHint annotation by stating 'read-only'. It adds that the tool selects and runs one of the operations, which is a dispatcher behavior. However, it does not disclose other behavioral aspects such as error handling, pagination, or return format, which are not covered by annotations. Since annotations already cover the read-only nature, the description adds minimal extra value.
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?
The description is a single, compact sentence that front-loads the tool's purpose. It is efficient with no redundant words.
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 distinct operations, each having different required parameters (siteId for get-project, teamSlug/projectNameSearchValue for get-projects, siteId/formId for get-forms-for-project). The description does not explain how to construct the selectSchema object, which operation to choose in which scenario, or what to expect in return. Given the complexity and absence of an output schema, this is a significant gap for an agent to use the tool correctly.
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 provides no explanation of the selectSchema parameter or its nested structure. With schema description coverage at 0%, the agent must infer the meaning of siteId, teamSlug, formId, etc. solely from the schema itself. The description only lists operation names, which does not convey the required parameters or their semantics.
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 clearly states the tool's function: to select and run one of three Netlify read operations (get-project, get-projects, get-forms-for-project). It uses a specific verb and resource, and the operation names distinguish it from sibling tools for other service types. However, it does not explicitly mention 'project services' but the name implies it.
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?
The description does not provide any guidance on when to use this tool versus its siblings (e.g., netlify-user-services-reader, netlify-team-services-reader). It lists the operations but does not explain the context for choosing this tool over others, nor any exclusions. The only implicit hint is the 'project' in the tool name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.