Skip to main content
Glama
asachs01

Autotask MCP Server

autotask_delete_service_call

Destructive

Permanently delete a service call and its associated data from Autotask. This irreversible action removes the record entirely.

Instructions

⚠ DESTRUCTIVE — IRREVERSIBLE. Permanently deletes a service call and all associated data. This action cannot be undone. Confirm with the user before invoking.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serviceCallIdYesThe service call ID to delete

Implementation Reference

  • The dispatch entry in the handler that delegates to autotaskService.deleteServiceCall() and returns the result.
    ['autotask_delete_service_call', async (a) => {
      await s.deleteServiceCall(a.serviceCallId);
      return { result: a.serviceCallId, message: `Successfully deleted service call ${a.serviceCallId}` };
    }],
  • Schema definition for autotask_delete_service_call with input schema requiring serviceCallId, marked as destructive.
    name: 'autotask_delete_service_call',
    description:
      '⚠ DESTRUCTIVE — IRREVERSIBLE. Permanently deletes a service call ' +
      'and all associated data. This action cannot be undone. ' +
      'Confirm with the user before invoking.',
    annotations: {
      title: 'Delete service call (irreversible)',
      readOnlyHint: false,
      destructiveHint: true,
      idempotentHint: false,
      openWorldHint: true,
    },
    inputSchema: {
      type: 'object',
      properties: {
        serviceCallId: {
          type: 'number',
          description: 'The service call ID to delete'
        }
      },
      required: ['serviceCallId']
    }
  • The tool is registered under the 'service_calls' category in TOOL_CATEGORIES.
    service_calls: {
      description: 'Service call dispatching, ticket linking, and resource assignments',
      tools: ['autotask_search_service_calls', 'autotask_get_service_call', 'autotask_create_service_call', 'autotask_update_service_call', 'autotask_delete_service_call', 'autotask_search_service_call_tickets', 'autotask_create_service_call_ticket', 'autotask_delete_service_call_ticket', 'autotask_search_service_call_ticket_resources', 'autotask_create_service_call_ticket_resource', 'autotask_delete_service_call_ticket_resource']
  • The service layer method that calls the HTTP client to DELETE /ServiceCalls/{id}.
    async deleteServiceCall(id: number): Promise<void> {
      const http = await this.ensureClient();
      try {
        this.logger.debug(`Deleting service call ${id}`);
        await http.delete('ServiceCalls', id);
        this.logger.info(`Service call ${id} deleted`);
      } catch (error) {
        this.logger.error(`Failed to delete service call ${id}:`, error);
        throw error;
      }
Behavior5/5

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

Beyond the destructiveHint annotation, the description adds 'IRREVERSIBLE', 'all associated data', and 'cannot be undone', providing critical behavioral context that the annotation alone does not convey.

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 two sentences with a prominent warning symbol, front-loading the destructive nature. Every word adds value, with no redundancy.

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?

Given the single parameter, no output schema, and clear annotations, the description fully covers the tool's behavior and necessary precautions.

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 coverage is 100% and the parameter is straightforward (serviceCallId). The description adds no additional meaning beyond what the schema already provides, meeting the baseline.

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 explicitly states 'Permanently deletes a service call' with clear verb and resource, distinguishing it from sibling tools which are create, update, or search operations.

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

Usage Guidelines4/5

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

It instructs to confirm with the user before invoking, which is a clear usage guideline for a destructive action. It does not explicitly mention when not to use or alternatives, but the simplicity of the operation makes this sufficient.

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/asachs01/autotask-mcp'

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