Skip to main content
Glama
Kong

Kong Konnect MCP Server

Official
by Kong

list_control_planes

List all control planes in your Kong Konnect organization with pagination and filters for name, cluster type, labels, and sorting.

Instructions

List all control planes in your organization.

INPUT:

  • pageSize: Number - Number of control planes per page (1-1000, default: 10)

  • pageNumber: Number (optional) - Page number to retrieve

  • filterName: String (optional) - Filter control planes by name

  • filterClusterType: String (optional) - Filter by cluster type (kubernetes, docker, etc.)

  • filterCloudGateway: Boolean (optional) - Filter by cloud gateway capability

  • labels: String (optional) - Filter by labels (format: 'key:value,existCheck')

  • sort: String (optional) - Sort field and direction (e.g. 'name,created_at desc')

OUTPUT:

  • metadata: Object - Contains pageSize, pageNumber, totalPages, totalCount, filters, sort

  • controlPlanes: Array - List of control planes with details for each including:

    • controlPlaneId: String - Unique identifier for the control plane

    • name: String - Display name of the control plane

    • description: String - Description of the control plane

    • type: String - Type of the control plane

    • clusterType: String - Underlying cluster type

    • controlPlaneEndpoint: String - URL endpoint for the control plane

    • telemetryEndpoint: String - URL endpoint for telemetry

    • hasCloudGateway: Boolean - Whether cloud gateway is enabled

    • labels: Object - Labels assigned to this control plane

    • metadata: Object - Creation and update timestamps

  • usage: Object - Information about how to use these results

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort field and direction (e.g. 'name,created_at desc')
labelsNoFilter by labels (format: 'key:value,existCheck')
pageSizeNoNumber of control planes per page
filterNameNoFilter control planes by name (contains)
pageNumberNoPage number to retrieve
filterClusterTypeNoFilter by cluster type (e.g., 'kubernetes', 'docker')
filterCloudGatewayNoFilter by cloud gateway capability
Behavior5/5

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

With no annotations provided, the description carries full burden and comprehensively discloses behavior: pagination, filtering, output structure. It clearly indicates a read-only list operation with no destructive hints.

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?

The description is well-structured with INPUT/OUTPUT sections and bullet points. It is front-loaded with the core purpose, though the output list is fairly detailed. Could be slightly more concise.

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

Completeness5/5

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

Given 7 parameters, no output schema, and no annotations, the description fully covers input options and output structure, including pagination metadata. It is complete for a list endpoint.

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 coverage is 100% and repeats the same descriptions (e.g., labels format, pageSize default). The description adds minimal new meaning beyond ensuring clarity in the structured input section.

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 clearly states 'List all control planes in your organization,' which is a specific verb+resource pair. It distinguishes itself from sibling tools like get_control_plane (singular) by implying a plural listing operation.

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 (e.g., get_control_plane for a single resource). It lists filters but does not explain scenarios where filtering is preferred over other tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Kong/mcp-konnect'

If you have feedback or need assistance with the MCP directory API, please join our Discord server