Skip to main content
Glama
rlowndes9

Zendesk MCP Server

by rlowndes9

find_trigger_conflicts

Read-onlyIdempotent

Detect pairs of active triggers with conflicting effects, such as overwriting the same field or setting and removing a tag. Scope by trigger ID or include inactive rules for cleanup audits.

Instructions

Surface pairs of active triggers that fight each other, same all-block precondition signature with contradicting effects. Two classes: field_overwrite (both write different values to the same field) and tag_set_remove_pair (one sets a tag, the other removes it). Pass trigger_id to scope to conflicts involving one rule, or include_inactive: true for cleanup audits. For a full trigger hygiene report (conflicts plus orphaned references, deactivated-but-referenced, ordering anomalies, empty rules), call audit_trigger_health instead, it bundles this analyzer with the support-kind checks. Operates over the cached verbose corpus, no extra HTTP.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refreshNoBypass cache and re-fetch triggers from Zendesk
instanceNoOverride the sticky instance for this call
trigger_idNoOptional: only return conflicts involving this trigger id
include_inactiveNoInclude deactivated triggers in conflict scan (default false). Useful for cleanup audits where dead rules still count.
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint. Description adds operational detail: 'Operates over the cached verbose corpus, no extra HTTP.' No contradictions.

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

Conciseness4/5

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

Three sentences, front-loaded with purpose, then details, then usage guidance. Efficient but could be slightly tighter. No wasted words.

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

Completeness5/5

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

For a 4-parameter tool with no output schema, the description explains what results contain (conflict pairs with classes), cache behavior, and usage context. References sibling for broader report. Fully sufficient.

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?

Schema description coverage is 100%, so baseline is 3. The description repeats schema info for trigger_id and include_inactive but does not add new meaning beyond the schema.

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 states the specific purpose: 'Surface pairs of active triggers that fight each other, same all-block precondition signature with contradicting effects.' It names two conflict classes and distinguishes from sibling tool `audit_trigger_health`.

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

Usage Guidelines5/5

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

Explicit guidance: 'Pass trigger_id to scope to conflicts involving one rule, or include_inactive: true for cleanup audits.' Also directly recommends sibling: 'For a full trigger hygiene report... call audit_trigger_health instead.'

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/rlowndes9/zendesk-mcp-server'

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