Skip to main content
Glama
CodesWhat

portkey-admin-mcp

by CodesWhat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_integrations

Read-onlyIdempotent

Lists org-level AI provider connections with optional workspace, type, or tag filters so you can find integration slugs before updating models or workspaces.

Instructions

List org-level AI provider connections with optional workspace, type, or tag filters. Use this to find integration slugs before model or workspace updates. Returns total plus id, name, slug, provider, status, description, workspace counts, and config summary.

Input Schema

NameRequiredDescriptionDefault
tagsNoMatch integrations that carry all supplied tags
typeNoFilter by integration type: 'workspace', 'organisation', or 'all' (default)
page_sizeNoNumber of results per page (default 100, max 100)
current_pageNoZero-based page number; the first page is 0
workspace_idNoFilter integrations accessible by a specific workspace

Output 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. Changed2 schema fields changedv1.0.9
    • 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"
  2. Changed1 schema field changedv0.13.0
    • addedInput schema / properties / tags
      Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "description": "Match integrations that carry all supplied tags",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
  3. Changed3 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
  4. 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"
  5. Addedv1.0.1
  6. Removed
  7. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds genuine value beyond that by disclosing the org-level scope and the returned payload shape (total, id, name, slug, provider, status, workspace counts, config summary), which tells the agent it is an enumerating read. It does not discuss empty results or how pagination interacts with the total count.

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?

Three sentences, front-loaded with the operation and scope, then the use case, then the return shape. Slightly wasteful since the return-field list largely duplicates what the output schema already provides, but nothing is genuinely off-topic.

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 zero-required-parameter, read-only list tool with full schema coverage, annotations, and an output schema, this covers what the agent needs to choose and call it. The only soft spot is the mild tension between 'org-level' in the description and the 'workspace'/'all' values of the type filter, which the description does not reconcile.

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 enum for type, the tag matching semantics, and the zero-based paging are already documented in the schema. The description only restates that workspace/type/tag filters exist and says nothing new about them, which is exactly the baseline-3 case.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('List') plus a precise resource ('org-level AI provider connections') and enumerates the filter dimensions. An agent can distinguish it from a single-record fetch like get_integration, though it never explicitly names a sibling such as list_mcp_integrations to rule out confusion with other list endpoints.

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?

'Use this to find integration slugs before model or workspace updates' gives a concrete pre-condition and downstream task, effectively pointing at update_integration_models / update_integration_workspaces without naming them. There are no explicit when-not exclusions, so it falls short of a full routing statement.

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