kinsta_tools_search-and-replaceSearch and replace database values in a Kinsta environment. Preview the changes before applying them to prevent unintended modifications.
Preview or perform a database search and replace. perform_replacement defaults to false for a safe preview.
| Name | Required | Description | Default |
|---|---|---|---|
| search | Yes | ||
| replace | Yes | ||
| environment_id | Yes | The environment ID | |
| is_clear_cache | No | ||
| perform_replacement | No |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already flag destructiveHint=true, and the description adds the key safeguard that replacement is opt-in via perform_replacement. It clearly communicates the preview/perform duality, which is exactly the behavioral nuance an agent needs. There is no contradiction with the annotations.
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 two short sentences with no filler. It front-loads the core purpose and then delivers the most important safety-relevant default.
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 destructiveHint annotation and the absence of an output schema, the description could explain what a preview returns or whether search supports regex/plain text. Still, it provides enough for an agent to make a safe first preview call, though cache-clearing behavior and output details remain unspecified.
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 only 20%, so the description must compensate for undocumented parameters. It adds meaning only to perform_replacement by framing it as a safe-preview toggle; search, replace, and is_clear_cache remain semantically thin beyond their names.
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 operation ('Preview or perform a database search and replace') with a clear verb and resource. This distinguishes it from the sibling tools, none of which offer search-and-replace functionality.
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 gives practical guidance by noting that perform_replacement defaults to false for a safe preview, implying the agent should first run in preview mode. It does not explicitly discuss exclusions or alternatives, but no sibling tool provides this capability, so the context is adequate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.