delete_variable
Delete a variable from a project by specifying its variable slug.
Instructions
Deletes a variable from a project
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| variableSlug | Yes |
Delete a variable from a project by specifying its variable slug.
Deletes a variable from a project
| Name | Required | Description | Default |
|---|---|---|---|
| variableSlug | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description must fully disclose behavior. It only says 'deletes,' implying a destructive action, but does not mention irreversibility, impact on related entities, or required permissions.
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 extremely concise (6 words) but at the expense of essential information. It is under-specified rather than efficiently informative.
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 a simple delete tool with one parameter, the description fails to cover key aspects: no output schema, no mention of success/error responses, and no context on side effects or constraints.
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?
With 0% schema coverage and no parameter descriptions, the single required parameter 'variableSlug' is completely unexplained. The description does not indicate what it is or how to obtain it.
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 clearly states the action (deletes) and resource (variable), distinguishing it from sibling tools like update_variable or rollback_variable. However, it lacks specificity about what a 'variable' is in this context.
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 guidance is provided on when to use this tool versus alternatives such as delete_variable_environment_value or rollback_variable. The agent receives no decision support.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/keyshade-xyz/keyshade-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server