tmaker_deleteDeletes a saved Template Maker project.
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Synonym for design_id or project_id. | |
| action | Yes | Operation to run. Each oneOf entry describes one action and lists its parameters. | |
| confirm | Yes | Pass true only after the user approves this change. Required by: project_delete. | |
| project_id | No | Saved project id from project_list. |
Changes observed during successful MCP inspections.
Input schema / requiredPrevious value: -[
- "action"
-]New value: +[
+ "action",
+ "confirm"
+]Input schema / properties / action / oneOfPrevious value: -[
- {
- "const": "project_delete",
- "description": "Deletes a saved project (id in project_id or id). Required: confirm. Optional: project_id, id."
- }
-]New value: +[
+ {
+ "const": "project_delete",
+ "description": "Deletes a saved project (id in project_id or id). Required: project_id or id, confirm."
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true, readOnlyHint=false, openWorldHint=false, so the safety profile is known. The description adds nothing beyond that: it does not say the deletion is irreversible, what exactly is removed (project plus its pages/assets?), or how the required confirm flag gates execution.
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?
A single front-loaded sentence with no filler, which is structurally clean, but its brevity reflects under-specification rather than efficiency — nothing is said that the name and title do not already convey.
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 an irreversible destructive operation with four parameters (including a numeric/enum indirection between id and project_id), the description omits irreversibility, confirmation semantics, and failure behavior. The rich schema mitigates this, but the description itself is too thin for the risk level.
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%, including the id/project_id synonym relationship and the confirm approval requirement, so the schema does the heavy lifting. The description contributes no additional parameter meaning, making the baseline 3 appropriate.
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?
States a specific verb and resource ("Deletes a saved Template Maker project"), but it is essentially a restatement of the title and adds no differentiation from the many sibling delete tools (templates_delete, apps_delete, content_delete, etc.). An agent cannot tell from the description alone how this differs from templates_delete.
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?
There is no guidance on when to use this tool versus tmaker_write or templates_delete, and no mention of prerequisites such as needing a project_id from tmaker_read/project_list or user approval before proceeding. The only 'when' information lives in the schema's confirm description, not the tool description.
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.