Skip to main content
Glama

delete_promo_code

Delete a promo code permanently by providing its ID. This action is irreversible.

Instructions

Permanently delete a promo code. This cannot be undone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promo_code_idYesThe promo code ID to delete.
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It clearly states the destructive nature ('Permanently delete', 'cannot be undone'), which is critical behavioral transparency. However, it omits potential side effects like cascading deactivations or authentication requirements, but for a simple delete operation this is acceptable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise, consisting of two short sentences with no extraneous words. The key information (action and consequence) is front-loaded, making it efficient for an AI agent to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter delete tool without output schema, the description is largely complete. It covers the action and irreversibility. A minor gap is whether the promo code can be deleted if it is in use, but this is not critical for basic usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema provides complete coverage (100%) for the single parameter, including a description. The tool description does not add any additional semantic information about the parameter beyond what the schema already provides, so a baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'delete' and the resource 'promo code', distinguishing it from sibling tools like 'update_promo_code' or 'get_promo_code'. The action is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions permanence and irreversibility, which implies careful usage, but it does not explicitly state when to use this tool versus alternatives such as 'update_promo_code' for deactivation. No alternative guidance is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/furkankoykiran/whop-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server