remove_pluginRemoves a plugin from a site (two steps). Its data stays exportable in the app for 30 days.
| Name | Required | Description | Default |
|---|---|---|---|
| site | Yes | ||
| plugin_id | Yes | ||
| confirm_token | No |
| Name | Required | Description | Default |
|---|---|---|---|
| agent_message | No | ||
| confirm_token | No | ||
| upcoming_bookings | No |
Changes observed during successful MCP inspections.
Output schema / properties / agent_messageAdded value: +{
+ "type": "string"
+}Output schema / properties / upcoming_bookingsAdded value: +{
+ "type": "number"
+}Input schema / properties / plugin_id / descriptionRemoved value: -"From list_plugins"Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "confirm_token": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+}Input schema / properties / confirm_token / descriptionRemoved value: -"After the user's yes"Input schema / properties / site / descriptionRemoved value: -"Site name"Input schema / properties / confirm_token / descriptionPrevious value: -"From the first call, once the user said yes"New value: +"After the user's yes"Input schema / properties / site / descriptionPrevious value: -"Site name, e.g. brave-otter-4821"New value: +"Site name"Output schema / (root)Previous value: -{
- "additionalProperties": {},
- "properties": {
- "agent_message": {
- "type": "string"
- },
- "confirm_token": {
- "type": "string"
- },
- "error": {
- "description": "On failure (isError): {code, message}"
- }
- },
- "type": "object"
-}New value: +nullDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare destructiveHint=true and non-idempotent behavior, so the description adds valuable context: the two-step nature of the operation and the 30-day exportable data retention. It does not cover permissions or error behavior, but the added details are meaningful beyond 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?
Two short sentences front-load the action and then add a key behavioral note. Every sentence earns its place with no unnecessary detail.
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 description covers the core action, the two-step process, and data retention, which are important for a destructive tool. However, with no parameter descriptions and no explanation of how the confirm_token fits into the two steps, an agent lacks enough information to invoke it 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?
Schema description coverage is 0%, so the description must explain the three parameters. It mentions 'two steps' but never clarifies the roles of 'site', 'plugin_id', or 'confirm_token', leaving the agent without any semantic guidance for constructing the call.
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 and resource: 'Removes a plugin from a site.' This clearly distinguishes it from add_plugin, update_plugin, and list_plugins, though it does not explicitly name alternatives or scope constraints for the site.
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?
It implies a two-step removal process and notes that data remains exportable for 30 days, giving some context for when and how to use it. However, it provides no explicit guidance on when to use this tool versus update_plugin or other sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.