Skip to main content
Glama
lazyants

hetzner-mcp-server

by lazyants
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Primary IP Actions

hetzner_list_primary_ip_actions
Read-onlyIdempotent

List all actions performed on a specific primary IP, such as assign, unassign, and rDNS changes, to audit or troubleshoot IP configuration.

Instructions

List all actions performed on a specific primary IP, such as assign, unassign, and rDNS changes.

Input Schema

NameRequiredDescriptionDefault
idYesPrimary IP ID
pageNoPage number
sortNoSort field, e.g. "id:asc" or "name:desc"; pass an array for multiple sort fields
statusNoFilter by action status: "running", "success", or "error"; pass an array for multiple statuses
per_pageNoResults per page (max 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv3.0.0
    • addedInput schema / properties / sort / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]
    • changedInput schema / properties / sort / description
      Previous value: -"Sort field, e.g. \"id:asc\" or \"name:desc\""New value: +"Sort field, e.g. \"id:asc\" or \"name:desc\"; pass an array for multiple sort fields"
    • removedInput schema / properties / sort / type
      Removed value: -"string"
    • addedInput schema / properties / status / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]
    • changedInput schema / properties / status / description
      Previous value: -"Filter by action status: comma-separated list of \"running\", \"success\", \"error\""New value: +"Filter by action status: \"running\", \"success\", or \"error\"; pass an array for multiple statuses"
    • removedInput schema / properties / status / type
      Removed value: -"string"
  2. First observedv2.2.0

TDQS

A3.5/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, so the safety profile is covered. The description adds which action types appear in the results, which is useful context, but says nothing about pagination behavior or result retention beyond what the schema already shows.

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 front-loaded sentence with zero filler; the resource and scope come first, followed by concrete action examples. Nothing is wasted.

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

Completeness3/5

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

There is no output schema, so the description ideally would hint at the shape of returned action records, but it only names examples. Combined with the lack of pagination notes, it is adequate but has clear gaps for an agent interpreting results.

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 fully documents id, page, sort, status, and per_page. The description only adds that the id must refer to a primary IP, which is marginal over the schema's own 'Primary IP ID'. Baseline 3 applies when the schema does the heavy lifting.

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?

Clear specific verb+resource: lists actions performed on a specific primary IP, with concrete action examples (assign, unassign, rDNS changes). It doesn't explicitly distinguish itself from sibling list tools like hetzner_list_primary_ips or the other *_actions lister tools, but the purpose is unambiguous.

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?

Usage is implied (audit/history of actions scoped to one primary IP via the required id), but there is no explicit when-to-use guidance, no mention of the alternative listers (e.g. list_primary_ips for the IPs themselves), and no note about pagination or result limits despite page/per_page params.

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