kinsta_domains_listRetrieve all custom domains assigned to a specific environment by providing its ID.
List all custom domains for an environment.
| Name | Required | Description | Default |
|---|---|---|---|
| env_id | Yes | The environment ID |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, covering the safety profile. The description adds the 'all' scope and environment association but provides no extra behavioral details such as pagination, ordering, or response shape; this is adequate but not rich.
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 clear sentence with no filler. Every word contributes to identifying the operation, the resource, and the scope.
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 simple: one fully documented required parameter stages and read-only/idempotent annotations make selection and invocation straightforward. The lack of an output schema and return-format description is a minor gap for a basic list operation.
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 100% for the only parameter, env_id. The description's phrase 'for an environment' echoes the schema rather than adding new semantic detail, so with full schema coverage the baseline score of 3 applies.
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 a specific verb, 'List', and names the exact resource, 'custom domains', with a clear scope: 'for an environment.' This distinguishes it from domain mutation tools like kinsta_domains_add and kinsta_domains_delete, and from DNS-domain tools like kinsta_dns_domains.
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 context is clear: this is a read-only listing operation for a single environment. However, it does not explicitly state when to use it over related alternatives such as kinsta_dns_domains or kinsta_domains_verification, so some inference is required.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.