Skip to main content
Glama

List Kong entities

kong_list

List Kong entities from the Admin API with tag filtering and pagination. Optionally fetch all items across pages automatically.

Instructions

List entities of a given type from the Kong Admin API (GET on a collection). Supports filtering by tags and offset pagination. Use fetch_all to automatically follow pagination and return every item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sizeNoPage size (number of items per page, default 100, max 1000).
tagsNoFilter by tags. Multiple tags are AND-combined (comma semantics).
entityYesThe Admin API collection path. Plain entity name (e.g. 'services', 'routes', 'consumers', 'plugins', 'upstreams', 'certificates') or a nested collection path (e.g. 'upstreams/my-upstream/targets', 'services/my-service/routes', 'consumers/bob/key-auth'). Common values: services, routes, consumers, consumer_groups, plugins, upstreams, certificates, ca_certificates, snis, vaults, keys, key-sets, workspaces, acls, tags, upstreams/<upstream>/targets, services/<service>/routes, services/<service>/plugins, routes/<route>/plugins, consumers/<consumer>/plugins, consumers/<consumer>/key-auth, consumers/<consumer>/basic-auth, consumers/<consumer>/jwt, consumers/<consumer>/hmac-auth, consumers/<consumer>/acls, rbac/roles, rbac/users, admins, groups, event-hooks, developers.
offsetNoPagination cursor returned as `offset` by a previous page.
fetch_allNoIf true, automatically follow pagination and return all items in a single array. Ignores offset.
workspaceNoEE workspace to scope this request to. Overrides the configured default workspace. Leave empty for OSS or the 'default' workspace.
Behavior4/5

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

Discloses it performs a GET on a collection, supports filtering by tags, pagination, and the fetch_all option. Since no annotations are provided, the description carries the burden. Lacks details on response structure or authentication, but covers key behaviors.

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?

Two sentences that are front-loaded, clear, and contain no wasted words. The description efficiently conveys the core purpose and a key usage note.

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?

For a listing tool with 6 parameters and no output schema, the description covers essential behavior (GET collection, tags, pagination, fetch_all). It could be enhanced with response format details or error notes, but is sufficient for an AI agent.

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 description adds only marginal value beyond the schema. The main description reiterates tags and pagination but does not provide new parameter-specific insights. Baseline of 3 is appropriate.

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?

Clearly states verb (List), resource (entities of a given type from Kong Admin API), and distinguishes from siblings like kong_get (single entity) and kong_create. The mention of fetch_all further clarifies the tool's scope.

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?

Provides usage guidance for the fetch_all parameter but does not explicitly compare with other sibling tools like kong_get or kong_create. However, the description implies the tool is for collection listing, which is sufficient.

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/Monohitoxx/kongapigateway-mcp-server'

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