delete_trigger
Delete a Zendesk trigger without affecting tickets previously modified by it.
Instructions
Delete a trigger. Tickets previously modified by it are unaffected.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Trigger ID to delete |
Delete a Zendesk trigger without affecting tickets previously modified by it.
Delete a trigger. Tickets previously modified by it are unaffected.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Trigger ID to delete |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses that tickets previously modified by the trigger are unaffected, which is a relevant behavioral trait. With no annotations, this adds value. Missing details on reversibility or 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?
Two short, front-loaded sentences with no wasted words. Every sentence serves a clear purpose.
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 deletion tool with one parameter and no output schema, the description is nearly complete. It provides the core action and a key behavioral note, but could mention permissions or permanence.
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% with 'Trigger ID to delete' for the id parameter. The description adds no further meaning beyond the schema, so baseline score is 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?
The description clearly states 'Delete a trigger.' which is a specific verb and resource. It distinguishes from sibling tools like delete_article or delete_automation by targeting triggers.
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 on when to use this tool versus alternatives (e.g., update_trigger or other delete tools). Lacks context about prerequisites or excluded scenarios.
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/SShadowS/zendesk-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server