Nginx Proxy Manager MCP

Overview Schema Source Related Servers Discussions Admin

List Certificates

list_certificates

List SSL certificates managed by Nginx Proxy Manager with domains and expiry details. Filter by domain substring or compact mode to inspect certificates without requesting or renewing them.

Instructions

List SSL certificates known to NPM, including expiry information when provided by NPM. Use this to inspect available certificates; create_letsencrypt_cert requests a new certificate and renew_certificate renews an existing one. This is read-only and makes no certificate request. Filter domain names by a case-insensitive substring with domain. Set compact=True to return only summary fields. Returns certificate objects with IDs, domains, provider, and expiry fields.

Input Schema

Name	Required	Description	Default
`domain`	No	Case-insensitive substring to match against any domain name; omit for all domains.
`compact`	No	Return only summary fields when True; defaults to full NPM objects.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.6.0Oct 18, 2026

addedInput schema / properties / compact

Added value: +{
+  "default": false,
+  "description": "Return only summary fields when True; defaults to full NPM objects.",
+  "type": "boolean"
+}

addedInput schema / properties / domain

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Case-insensitive substring to match against any domain name; omit for all domains."
+}

First observedv0.5.1Oct 16, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it declares 'read-only', states 'makes no certificate request', notes expiry is included only 'when provided by NPM', and enumerates return fields. It stops short of auth requirements or pagination behavior, so not a 5.

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?

Front-loaded with purpose and sibling routing, then filtering and return-shape details. Four sentences, each carrying content, though the return-fields sentence is somewhat redundant given an output schema exists.

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?

Covers purpose, alternatives, filtering, and return contents for a two-optional-param read tool, and the output schema covers return shape. Missing only minor operational context such as pagination or any auth prerequisites, which keeps it from a 5.

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 schema already documents both `domain` (case-insensitive substring) and `compact` (summary fields only). The description restates exactly those semantics without adding format, edge-case, or defaulting detail beyond the schema. Baseline 3 applies.

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?

States a specific verb + resource ('List SSL certificates known to NPM') with a scoping note about expiry data. It also names the sibling tools it is not (create_letsencrypt_cert, renew_certificate), so an agent can distinguish it without opening any schema.

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?

Explicitly routes the agent: 'Use this to inspect available certificates' while naming create_letsencrypt_cert for creation and renew_certificate for renewal. It also states the negative condition ('makes no certificate request'), leaving nothing to inference.

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