Skip to main content
Glama
Kong

Kong Konnect MCP Server

Official
by Kong
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

list_plugins

List all plugins associated with a control plane, including their names, enabled status, protocols, tags, and scope. Optionally paginate results or request raw configuration values.

Instructions

List all plugins associated with a control plane.

INPUT:

  • controlPlaneId: String - ID of the control plane

  • size: Number - Number of plugins to return (1-1000, default: 100)

  • offset: String (optional) - Pagination offset token from previous response

  • includeRawConfig: Boolean - Requests raw plugin configuration values. Defaults to false and only takes effect when the server policy env var allows raw config responses.

OUTPUT:

  • metadata: Object - Contains controlPlaneId, size, offset, nextOffset, totalCount, raw-config policy flags, and warnings when applicable

  • plugins: Array - List of plugins with details for each including:

    • pluginId: String - Unique identifier for the plugin

    • name: String - Name of the plugin (e.g., rate-limiting, cors, etc.)

    • enabled: Boolean - Whether the plugin is enabled

    • configIncluded: Boolean - Whether raw config values were included

    • configKeys: Array - Returned by default to summarize configuration without exposing raw values

    • configEntryCount: Number - Returned by default to summarize configuration size

    • config: Object - Raw plugin-specific configuration, only when includeRawConfig is explicitly true and server policy allows it

    • protocols: Array - Protocols this plugin applies to

    • tags: Array - Tags associated with the plugin

    • scoping: Object - Defines plugin scope including:

      • consumerId: String - Consumer this plugin applies to (if any)

      • serviceId: String - Service this plugin applies to (if any)

      • routeId: String - Route this plugin applies to (if any)

      • global: Boolean - Whether this is a global plugin

    • metadata: Object - Creation and update timestamps

  • relatedTools: Array - List of related tools for plugin configuration

Raw config is excluded by default. Raw config is only returned when includeRawConfig is explicitly true and the server is configured with KONNECT_ALLOW_RAW_PLUGIN_CONFIG=true. Even then, plugin configuration may contain sensitive values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sizeNoNumber of plugins to return
offsetNoOffset token for pagination (from previous response)
controlPlaneIdYesControl Plane ID (obtainable from list-control-planes tool)
includeRawConfigNoInclude raw plugin configuration values. Disabled by default because configuration may contain sensitive data.

Tool Definition Quality

A4.6/5.0
Behavior5/5

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

No annotations exist, so the description fully discloses behavior: raw config exclusion by default, enabling only with includeRawConfig=true and server env var, pagination via offset, size limits, and warnings about sensitive data. This exceeds what the schema provides.

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 long but well-structured with INPUT/OUTPUT sections. Each sentence is informative; some redundancy with schema (e.g., size default) but not excessive. Front-loaded purpose makes it easy to scan. Could be slightly more concise, but overall efficient.

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?

Despite lacking an output schema, the description fully details the output structure including conditional fields (config). It covers pagination, raw config behavior, and scoping fields. No gaps are evident for an agent to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds value by explaining includeRawConfig policy dependency and controlPlaneId as obtainable from another tool. It also clarifies the offset as a token from previous response. This adds useful context beyond schema.

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?

Description starts with 'List all plugins associated with a control plane' – a clear verb and resource. Sibling tools are all for different resources (control planes, consumers, routes, etc.), so this tool is distinct and unambiguously about plugins.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not explicitly state when to use this versus alternatives, but sibling tools cover different resources, making the context clear. The detailed input/output sections help the agent understand usage. Lacks explicit 'use when' or 'instead of' guidance, but the resource specificity is strong.

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