portkey-admin-mcp

update_integration_models

DestructiveIdempotent

Bulk enable or disable integration models, register custom or fine-tuned models with per-model hosts, headers, and static token pricing to control which models every workspace can use.

Instructions

Bulk enable or disable integration models, register custom or fine-tuned models, set per-model hosts and headers, and attach static token pricing. allow_all_models controls whether future provider models start enabled. These changes affect every workspace using the integration; inspect list_integration_models first and use get_model_pricing when deriving custom rates. Returns success and the number of models updated.

Input Schema

Name	Required	Description
`slug`	Yes	The slug of the integration
`models`	Yes	Array of model configurations to update
`allow_all_models`	No	Whether newly available provider models are enabled by default

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"

Changed5 schema fields changedAug 9, 2026

addedInput schema / properties / allow_all_models

Added value: +{
+  "description": "Whether newly available provider models are enabled by default",
+  "type": "boolean"
+}

addedInput schema / properties / models / items / properties / base_model_slug

Added value: +{
+  "description": "Base model slug for a fine-tuned model",
+  "type": "string"
+}

addedInput schema / properties / models / items / properties / configurations

Added value: +{
+  "description": "Per-model custom upstream host and headers",
+  "properties": {
+    "custom_headers": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "description": "Headers sent only for this model; values may contain secrets",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "custom_host": {
+      "description": "Custom upstream URL used only for this model",
+      "format": "uri",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / models / items / properties / is_finetune

Added value: +{
+  "description": "Whether this entry is a fine-tuned model",
+  "type": "boolean"
+}

addedInput schema / properties / models / items / properties / pricing_config

Added value: +{
+  "description": "Static custom pricing for this integration model",
+  "properties": {
+    "pay_as_you_go": {
+      "description": "Pay-as-you-go rates for this integration model",
+      "properties": {
+        "request_token": {
+          "description": "Input token pricing",
+          "properties": {
+            "price": {
+              "description": "Static price per token in the integration pricing unit",
+              "minimum": 0,
+              "type": "number"
+            }
+          },
+          "required": [
+            "price"
+          ],
+          "type": "object"
+        },
+        "response_token": {
+          "description": "Output token pricing",
+          "properties": {
+            "price": {
+              "description": "Static price per token in the integration pricing unit",
+              "minimum": 0,
+              "type": "number"
+            }
+          },
+          "required": [
+            "price"
+          ],
+          "type": "object"
+        }
+      },
+      "type": "object"
+    },
+    "type": {
+      "const": "static",
+      "description": "Static per-token pricing configuration",
+      "type": "string"
+    }
+  },
+  "required": [
+    "type"
+  ],
+  "type": "object"
+}

Addedv1.0.1May 7, 2026
RemovedMay 1, 2026
First observedJan 1, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare destructive, idempotent, open-world, and non-read-only behavior. The description adds important blast-radius context by stating changes affect every workspace using the integration, plus the future-model effect of allow_all_models and the return shape.

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?

The description is three tight sentences with the primary action front-loaded. It then covers the future-model flag, blast radius, prerequisites, and return value without unnecessary repetition.

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 destructive global mutation, it provides the key context: what it affects, related tools to inspect first, and what it returns. It does not clarify whether the models array merges or replaces existing model settings, nor does it mention permission requirements, leaving a small gap.

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 slug, models, and allow_all_models in detail. The description reinforces the high-level purpose of the models array and allow_all_models, but adds little syntax or behavioral detail beyond the schema.

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 uses specific verbs and resources: bulk enable/disable models, register custom or fine-tuned models, set per-model hosts and headers, and attach static token pricing. This clearly distinguishes the tool from siblings such as update_integration and list_integration_models.

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?

It gives useful prerequisites: inspect list_integration_models first and use get_model_pricing when deriving custom rates. It does not explicitly state when not to use this tool versus update_integration or delete_integration_model, so it falls short of full alternative routing.

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

Deploy Server