Skip to main content
Glama
influxdata

InfluxDB MCP Server

Official
by influxdata
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_admin_token

Creates a named InfluxDB admin token with full administrative permissions for Core or Enterprise, with optional name and expiration settings.

Instructions

Create a new InfluxDB named admin token with full administrative permissions (Core/Enterprise only). Named admin tokens can manage databases, users, and resource tokens, but cannot manage other admin tokens.

Input Schema

NameRequiredDescriptionDefault
nameNoOptional name for the admin token (e.g., "backup-admin-token"). If not provided, a unique name will be generated.
expiry_secsNoOptional expiration time in seconds. If omitted, the token doesn't expire.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.0
    • addedInput schema / properties / expiry_secs
      Added value: +{
+  "description": "Optional expiration time in seconds. If omitted, the token doesn't expire.",
+  "minimum": 1,
+  "type": "number"
+}
  2. First observedv1.4.1-test.1

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description must carry behavioral disclosure. It usefully states permission scope and an important limitation (cannot manage other admin tokens), but it omits auth requirements and how the generated token secret is handled, which are important for a privileged credential tool.

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 no wasted words. The key purpose, permission scope, edition restriction, and limitation are all communicated efficiently.

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?

For a privileged credential-creation tool with no annotations and no output schema, the description covers purpose and permission boundaries but omits auth prerequisites and return-value behavior (e.g., whether the token secret is surfaced). It is adequate but incomplete for safe 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%, so both optional parameters are already well documented. The description adds no additional parameter syntax or constraints beyond what the schema provides, warranting the baseline score.

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 names a specific verb ('Create'), resource ('InfluxDB named admin token'), and scope ('full administrative permissions'), with parenthetical edition gating. It also distinguishes what the token can and cannot manage, making the purpose 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?

The description implies creation of an admin token and notes Core/Enterprise-only availability, but does not explicitly state when to choose this over sibling tools like cloud_create_database_token or regenerate_operator_token. Usage is inferable but not guided.

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