portkey-admin-mcp

list_mcp_integrations

Read-onlyIdempotent

Discover MCP integration IDs by listing paginated integrations in your organization, filtered by name, workspace, organisation, or ownership. Use it before fetching a single integration's config.

Instructions

List MCP integrations in the organization. Returns paginated integration records plus total and has_more for discovering integration IDs; use get_mcp_integration for one integration's full Portkey-side config and list_mcp_servers for the servers under an integration.

Input Schema

Name	Required	Description
`type`	No	Filter by workspace, organisation, or all integration ownership
`search`	No	Search integrations by name
`page_size`	No	Number of results per page (max 1000)
`current_page`	No	Zero-based page number; the first page is 0
`workspace_id`	No	Filter by workspace ID
`organisation_id`	No	Filter by organisation UUID

Output Schema

Name	Required	Description
`ok`	Yes	Whether the tool call succeeded and returned structured data
`data`	No	Structured success payload when ok is true
`error`	No	Structured error payload when ok is false

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.0.9Oct 26, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed8 schema fields changedv0.11.5Sep 8, 2026

changedInput schema / properties / current_page / description

Previous value: -"Page number for pagination"New value: +"Zero-based page number; the first page is 0"

removedInput schema / properties / current_page / exclusiveMinimum
```
Removed value: -0
```
addedInput schema / properties / current_page / minimum
```
Added value: +0
```

addedInput schema / properties / organisation_id

Added value: +{
+  "description": "Filter by organisation UUID",
+  "type": "string"
+}

changedInput schema / properties / page_size / description

Previous value: -"Number of results per page (max 100)"New value: +"Number of results per page (max 1000)"

changedInput schema / properties / page_size / maximum
```
Previous value: -100New value: +1000
```

addedInput schema / properties / search

Added value: +{
+  "description": "Search integrations by name",
+  "type": "string"
+}

addedInput schema / properties / type

Added value: +{
+  "description": "Filter by workspace, organisation, or all integration ownership",
+  "enum": [
+    "workspace",
+    "organisation",
+    "all"
+  ],
+  "type": "string"
+}

Changed2 schema fields changedv0.5.0Jul 14, 2026
- addedInput schema / properties / current_page / maximum
```
Added value: +9007199254740991
```
- changedInput schema / properties / current_page / type
```
Previous value: -"number"New value: +"integer"
```
Addedv1.0.1May 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so safety is covered. The description adds behavior beyond them by disclosing the return shape (paginated records plus total and has_more), which tells the agent it must loop for full enumeration. It stops short of rate limits or ordering guarantees, so not a 5.

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, zero waste. The core action and return shape come first, then the disambiguation against siblings. Every clause earns its place in a tool list this crowded.

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?

With an output schema present and 100% parameter coverage, the description only needs to establish purpose and sibling routing, which it does. Minor gap: it does not hint at the filtering dimensions (workspace/organisation/type, search) that make this tool powerful, leaving the agent to discover them in the schema.

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% across all six parameters, including the type enum and the zero-based current_page note, so the schema carries full burden. The description adds no filter syntax or semantics beyond what is already structured. Baseline 3 applies.

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?

States a specific verb and resource ('List MCP integrations in the organization') and immediately distinguishes itself from two siblings by naming get_mcp_integration and list_mcp_servers with their distinct roles. An agent can select this without opening any schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use this for discovery of integration IDs, get_mcp_integration when you need one integration's full Portkey-side config, list_mcp_servers when you need the servers under an integration. That is a clear when-to-use-this vs when-to-use-alternatives statement, which is rare and valuable given the very large sibling set.

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

Deploy Server