Skip to main content
Glama

list_mcp_integrations

Read-onlyIdempotent

Lists MCP integrations in an organization with pagination, filters, and total counts so you can discover integration IDs and manage configurations.

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_mcp_integrations"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoMatch resources carrying all supplied tags
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

NameRequiredDescriptionDefault
okYesCall succeeded
dataNoSuccess payload
errorNoFailure details

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.16.5
    • changedOutput schema / properties / data / description
      Previous value: -"Structured success payload when ok is true"New value: +"Success payload"
    • changedOutput schema / properties / error / description
      Previous value: -"Structured error payload when ok is false"New value: +"Failure details"
    • changedOutput schema / properties / error / properties / details / description
      Previous value: -"Optional structured error details"New value: +"Extra error details"
    • changedOutput schema / properties / error / properties / message / description
      Previous value: -"Human-readable error message"New value: +"Error message"
    • changedOutput schema / properties / ok / description
      Previous value: -"Whether the tool call succeeded and returned structured data"New value: +"Call succeeded"
  2. Changed1 schema field changedv0.16.4
    • addedInput schema / properties / tags
      Added value: +{
      +  "additionalProperties": {
      +    "type": "string"
      +  },
      +  "description": "Match resources carrying all supplied tags",
      +  "propertyNames": {
      +    "pattern": "^[a-zA-Z0-9_-]+$",
      +    "type": "string"
      +  },
      +  "type": "object"
      +}
  3. 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"
  4. 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"
      +}
  5. 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"
  6. Addedv1.0.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds real value on top: it discloses the return shape (paginated records plus total and has_more) and the organization-level scope, though it says nothing about permissions or how has_more should drive subsequent calls.

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?

Two sentences, front-loaded with purpose and then routing. The pagination return clause ("total and has_more") is partially redundant with the existing output schema, which keeps it just short of a 5, but no sentence is filler.

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 7 optional params, a nested tags object, and an output schema already covering return values, the description supplies the parts that matter most: identity, scope, and sibling routing. The remaining gap is filter/pagination usage guidance, which is a minor omission given full schema coverage.

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 schema already documents all seven optional filters including the type enum and zero-based paging. The description adds no filter semantics beyond that — it never mentions tags, search, workspace_id, or how type interacts with the stated organization scope. Baseline 3 applies when the schema does the heavy lifting.

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") plus the scope ("in the organization"), and explicitly names the two adjacent tools it is not (get_mcp_integration for full config, list_mcp_servers for servers under an integration). An agent can select this tool 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?

Gives both the positive use case ("for discovering integration IDs") and named alternatives with the condition that selects each — full Portkey-side config goes to get_mcp_integration, per-integration server listings go to list_mcp_servers. Nothing is left to inference about which tool to reach for.

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