Retrieve Netlify extensions and their full details for your team. Query available extensions or fetch specific extension information by slug and team ID.
Select and run one of the following Netlify read operations (read-only) get-extensions, get-full-extension-details
| 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-extensions",
- "type": "string"
- },
- "params": {
- "additionalProperties": false,
- "properties": {},
- "type": "object"
- }
- },
- "required": [
- "operation"
- ],
- "type": "object"
- },
- {
- "additionalProperties": false,
- "properties": {
- "aiAgentName": {
- "type": "string"
- },
- "llmModelName": {
- "type": "string"
- },
- "operation": {
- "const": "get-full-extension-details",
- "type": "string"
- },
- "params": {
- "additionalProperties": false,
- "properties": {
- "extensionSlug": {
- "type": "string"
- },
- "teamId": {
- "description": "Team id of the current project team. If unsure, ask what Netlify team",
- "type": "string"
- }
- },
- "required": [
- "extensionSlug",
- "teamId"
- ],
- "type": "object"
- }
- },
- "required": [
- "operation"
- ],
- "type": "object"
- }
-]New value: +[
+ {
+ "properties": {
+ "aiAgentName": {
+ "type": "string"
+ },
+ "llmModelName": {
+ "type": "string"
+ },
+ "operation": {
+ "const": "get-extensions",
+ "type": "string"
+ },
+ "params": {
+ "properties": {},
+ "type": "object"
+ }
+ },
+ "required": [
+ "operation"
+ ],
+ "type": "object"
+ },
+ {
+ "properties": {
+ "aiAgentName": {
+ "type": "string"
+ },
+ "llmModelName": {
+ "type": "string"
+ },
+ "operation": {
+ "const": "get-full-extension-details",
+ "type": "string"
+ },
+ "params": {
+ "properties": {
+ "extensionSlug": {
+ "type": "string"
+ },
+ "teamId": {
+ "description": "Team id of the current project team. If unsure, ask what Netlify team",
+ "type": "string"
+ }
+ },
+ "required": [
+ "extensionSlug",
+ "teamId"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "operation"
+ ],
+ "type": "object"
+ }
+]v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already declares the tool is read-only, and the description reinforces this with 'read-only'. It adds the behavioral trait that it is a dispatcher that selects and runs one of two operations, which is beyond the annotation. However, it does not disclose any additional constraints (e.g., authentication, rate limits) or consequences of selecting an operation, so the added transparency is minimal.
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 concise sentence that front-loads the action ('Select and run') and lists the operations. It is efficient with no wasted words, though it could be slightly more structured by separating the operations or explaining them. The brevity is appropriate for a dispatcher tool.
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 complex with two distinct operations, yet the description does not explain the outcomes of each operation (e.g., list of extensions vs. detailed extension info) or the purpose of the required parameters. There is no output schema, so the agent cannot anticipate the return format. The description is insufficient for an agent to correctly choose and invoke an operation without additional inference.
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 schema has very low description coverage (0% per context signals), and the description does not explain any parameters. The only parameter-related content is the operation names listed, which hint at what inputs might be needed but not their semantics. For get-full-extension-details, the required extensionSlug has no description, and teamId only has a partial one; the description adds no meaning beyond what the schema already conveys.
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 the tool's role as a selector that runs Netlify read operations, and explicitly lists the two operations (get-extensions, get-full-extension-details). It is clearly specific to extension services, distinguishing it from sibling readers for other services. However, it does not describe what each operation returns (e.g., a list vs. details), so the purpose is clear but not fully detailed.
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 offers no guidance on when to use this tool versus the sibling readers (e.g., netlify-user-services-reader) or the extension updater. The agent must rely on the tool name and operation names to infer usage. There are no explicit exclusions or alternative tool references, leaving the selection decision to the agent's interpretation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.