kinsta_sftp-users_addCreate a new SFTP/SSH user for a Kinsta environment. Provide username, password, and optional read/write permissions to grant access.
Add a new additional SFTP/SSH user account to an environment.
| Name | Required | Description | Default |
|---|---|---|---|
| env_id | Yes | The environment ID | |
| password | Yes | Password for the new SFTP account (minimum 16 characters) | |
| username | Yes | Username for the new SFTP account | |
| permission | No | ||
| root_directory | No |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The openWorldHint annotation gives little information, and the description does not disclose what happens after creation, side effects, permission requirements, or whether the account is immediately active. For a mutation tool with no output schema, the description should provide more behavioral context, but it only says 'Add'.
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 sentence, front-loaded with the action and resource, and contains no filler. It is concise, though perhaps too short to carry needed guidance; structurally it is clean but slightly under-specified.
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 tool with 5 parameters, 3 required, one enum, and no output schema, the description is insufficient. It does not clarify how to obtain env_id, the meaning of 'additional', expected response, or how to handle optional parameters. The agent is left without enough context to call the tool confidently.
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 covers 3 of 5 parameters with descriptions, but the description itself adds no parameter semantics. It does not mention the 'permission' enum (read/write) or 'root_directory' parameter, leaving those 40% of parameters undocumented in both places. The description fails to compensate for the schema coverage 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 uses a specific verb 'Add' with a clear resource 'new additional SFTP/SSH user account' and scopes it to 'an environment'. It is easily distinguishable from sibling tools like kinsta_sftp-users_list, toggle, and remove, which serve different operations.
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 is given on when to use this tool versus alternatives such as kinsta_sftp-users_toggle or remove, nor any prerequisites like having an existing environment or checking current users. The description is a bare statement of intent with no context for selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.