netlify-user-services
Retrieve a Netlify user's account information through the user services tool.
Instructions
Select and run one of the following Netlify operations get-user
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| selectSchema | Yes |
Retrieve a Netlify user's account information through the user services tool.
Select and run one of the following Netlify operations get-user
| Name | Required | Description | Default |
|---|---|---|---|
| selectSchema | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations and the description provides no behavioral traits, side effects, permissions, or other important information beyond the operation name.
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 short but lacks necessary detail. It is under-specified and does not effectively convey the tool's purpose.
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?
Given the complexity (nested parameters, no schema descriptions, no output schema, no annotations), the description is severely incomplete.
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% and the description does not explain the parameters. The nested 'selectSchema' object is left entirely undocumented.
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 mentions the operation name 'get-user' but does not explain what it does. It is vague and does not clarify the action or result.
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?
No guidance on when to use this tool versus siblings. The description implies selection but lists only one operation, providing no context or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/jurgen-paul/netlify-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server