ESA MCP Server

delete_certificate

Remove SSL/TLS certificates from websites managed through ESA services to maintain security compliance and manage certificate lifecycles.

Instructions

Deletes a certificate for a website.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "siteId": "<siteId>",
      "id": "<id>"
    },
    "name": "delete_certificate"
  }
}

Input Schema

Name	Required	Description	Default
`siteId`	Yes	The website ID, which can be obtained by calling the ListSites operation. Example: 1234567890123
`id`	Yes	The ID of the certificate. Example: 30001303

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 18, 2025

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Deletes' implies a destructive operation, it doesn't specify whether this action is reversible, what permissions are required, or what happens to the website after deletion. For a destructive tool with zero annotation coverage, this leaves significant behavioral gaps.

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 a single, clear sentence that efficiently communicates the core purpose without any unnecessary words. It's appropriately sized and front-loaded with the essential information, making it easy to parse quickly.

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

Completeness2/5

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

Given this is a destructive operation with no annotations and no output schema, the description is incomplete. It doesn't address critical context like what the tool returns (e.g., success/failure confirmation), error conditions, or side effects on the website. For a deletion tool, this leaves too many unknowns for safe and effective use.

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 the input schema already fully documents both parameters (siteId and id) with descriptions and examples. The description adds no additional parameter information beyond what's in the schema, which is acceptable given the high schema coverage, resulting in the baseline score of 3.

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

Purpose4/5

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

The description clearly states the action ('Deletes') and the resource ('a certificate for a website'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'delete_record' or 'deployment_delete', which also perform deletion operations on different resources.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites (e.g., needing to list certificates first), when not to use it, or how it differs from other deletion tools like 'delete_record' or 'set_certificate' which might handle certificate-related operations differently.

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