Skip to main content
Glama
CodesWhat

portkey-admin-mcp

by CodesWhat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_mcp_integrations

Read-onlyIdempotent

Retrieve paginated MCP integration records with total and has_more status to discover integration IDs. Filter by workspace, organisation, ownership, search, and page size.

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

TableJSON Schema
NameRequiredDescriptionDefault
typeNoFilter by workspace, organisation, or all integration ownership
searchNoSearch integrations by name
page_sizeNoNumber of results per page (max 1000)
current_pageNoZero-based page number; the first page is 0
workspace_idNoFilter by workspace ID
organisation_idNoFilter by organisation UUID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the tool call succeeded and returned structured data
dataNoStructured success payload when ok is true
errorNoStructured error payload when ok is false

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.11.5
    • 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"
+}
  2. Changed2 schema fields changedv0.5.0
    • addedInput schema / properties / current_page / maximum
      Added value: +9007199254740991
    • changedInput schema / properties / current_page / type
      Previous value: -"number"New value: +"integer"
  3. Addedv1.0.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds behavioral value by stating the pagination output (total, has_more) and the use case of discovering integration IDs. This enriches the agent's understanding beyond the annotations.

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 sentence with three tightly packed clauses: core action, return/pagination details, and sibling routing. Every element earns its place and the most important information is front-loaded. No filler or redundancy.

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?

For a read-only listing tool with an output schema and full schema coverage for parameters, the description covers the key contextual needs: what it returns, pagination cues, and how to fetch more detail or related resources. The agent has enough information to select and call the tool correctly.

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 baseline is 3 without any parameter info in the description. The description does not add meaning beyond what the schema already provides for the six parameters. No parameter detail is missing, but the description also does not enhance it.

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 begins with a specific verb and resource: 'List MCP integrations in the organization.' It further clarifies the return shape (paginated records, total, has_more) and distinguishes itself from get_mcp_integration and list_mcp_servers. This makes the tool's purpose unambiguous and easily differentiated from siblings.

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?

The description explicitly names the alternatives and the conditions that select them: 'use get_mcp_integration for one integration's full Portkey-side config and list_mcp_servers for the servers under an integration.' This gives the agent clear routing guidance without needing to inspect schemas.

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