tiendanube_scripts_deleteDeletes a store script by ID via the Tiendanube API, so you can remove unwanted or outdated scripts from your store.
Remove a script from the store. HTTP: DELETE /scripts/{id} Required scope: write_scripts API version: 2025-03
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Store script ID |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true, so the description adds little behavioral value. It names the required scope, which is genuinely useful auth context, but it does not state that deletion is irreversible or what happens on an invalid/already-deleted id.
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?
Four short lines, front-loaded with the action, followed by endpoint, scope and API version. No filler.
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?
A one-param destructive tool with full schema coverage and rich annotations; scope and API version are given. Missing only confirmation-of-irreversibility and post-delete behavior, which is a minor gap at this complexity.
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 coverage is 100% and the single param 'id' is documented as 'Store script ID', so baseline 3 applies. The description adds no format or lookup guidance (e.g. obtainable from scripts_list) beyond the path template /scripts/{id}.
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?
Specific verb (Remove) and resource (a script from the store), with the exact endpoint DELETE /scripts/{id} reinforcing it. Distinguished from siblings tiendanube_scripts_create/update/get/list by name and semantics.
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 explicit when-to-use/when-not-to-use guidance and no mention of alternatives (e.g. update to modify, scripts_list to find the id). The required scope 'write_scripts' implies prerequisites, which is a partial substitute, but nothing about irreversible effects is stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.