Skip to main content
Glama
lazyants

hetzner-mcp-server

by lazyants
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Certificates

hetzner_list_certificates
Read-onlyIdempotent

List SSL/TLS certificates in a Hetzner Cloud project and filter by name, type, or label. Supports sorting and pagination for certificate inventory checks.

Instructions

List all SSL/TLS certificates in the project, with optional filtering.

Input Schema

NameRequiredDescriptionDefault
nameNoFilter by name
pageNoPage number
sortNoSort field, e.g. "id:asc" or "name:desc"; pass an array for multiple sort fields
typeNoFilter by certificate type
per_pageNoResults per page (max 50)
label_selectorNoLabel filter, e.g. "env=prod,tier=web"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.0
    • addedInput schema / properties / sort
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  ],
+  "description": "Sort field, e.g. \"id:asc\" or \"name:desc\"; pass an array for multiple sort fields"
+}
  2. First observedv2.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered. The description only adds the 'in the project' scope; it says nothing about pagination behavior or result ordering beyond what the schema fields imply.

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?

A single short sentence with zero filler, front-loading the verb, resource, scope, and the filtering capability. Nothing in it is redundant or padded.

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 read-only list tool with full schema coverage, no output schema, and complete annotations, the description is essentially sufficient. It could mention that results are paginated or that all fields are optional, but no critical gap prevents correct invocation.

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% – name, type enum, sort syntax, label_selector format, page and per_page are all documented in the schema. The description adds no parameter detail beyond 'optional filtering', so the baseline of 3 applies.

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?

States a specific verb+resource (list SSL/TLS certificates) and scopes it to the project, which is clearly distinct from the sibling hetzner_get_certificate and hetzner_list_certificate_actions. It does not explicitly name a sibling to differentiate from, so it stops short of a 5.

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 phrase 'with optional filtering' implies the tool can be narrowed but provides no when-to-use guidance, no prerequisites, and no routing to alternatives such as hetzner_get_certificate for a single cert. Usage is implied rather than stated.

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

Deploy Server

Other Tools