portkey-admin-mcp

create_workspace

Creates an isolated workspace to separate resources, API keys, and team members, auto-generating a slug when omitted and returning the new workspace ID, name, and slug.

Instructions

Create a workspace to isolate resources, API keys, and team members. If slug is omitted it is auto-generated from the name; returns the new workspace id, name, and slug.

Input Schema

Name	Required	Description
`name`	Yes	Name of the workspace
`slug`	No	URL-friendly slug (auto-generated if not provided)
`users`	No	Existing user IDs to add
`metadata`	No	Custom metadata key-value pairs
`is_default`	No	Set as default workspace (1 = yes, 0 = no)
`description`	No	Description of the workspace
`rate_limits`	No	Initial workspace rate-limit settings
`usage_limits`	No	Initial workspace usage-limit settings

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"

Changed1 schema field changedv0.12.2Oct 2, 2026

changedInput schema / properties / usage_limits / items / properties / next_usage_reset_at / anyOf

Previous value: -[
-  {
-    "format": "date-time",
-    "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "format": "date-time",
+    "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

Changed3 schema fields changedv0.11.5Sep 8, 2026

addedInput schema / properties / rate_limits

Added value: +{
+  "description": "Initial workspace rate-limit settings",
+  "items": {
+    "properties": {
+      "type": {
+        "description": "Whether the limit counts requests or tokens",
+        "enum": [
+          "requests",
+          "tokens"
+        ],
+        "type": "string"
+      },
+      "unit": {
+        "description": "Rate window: requests per day, hour, or minute",
+        "enum": [
+          "rpd",
+          "rph",
+          "rpm"
+        ],
+        "type": "string"
+      },
+      "value": {
+        "description": "Maximum count in the selected rate window",
+        "maximum": 9007199254740991,
+        "minimum": 0,
+        "type": "integer"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedInput schema / properties / usage_limits

Added value: +{
+  "description": "Initial workspace usage-limit settings",
+  "items": {
+    "properties": {
+      "alert_threshold": {
+        "description": "Percentage of the limit that triggers an alert",
+        "exclusiveMinimum": 0,
+        "type": "number"
+      },
+      "credit_limit": {
+        "description": "Maximum cost or token usage for the workspace",
+        "exclusiveMinimum": 0,
+        "type": "number"
+      },
+      "next_usage_reset_at": {
+        "anyOf": [
+          {
+            "format": "date-time",
+            "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Next reset timestamp in ISO 8601 format"
+      },
+      "periodic_reset": {
+        "anyOf": [
+          {
+            "enum": [
+              "monthly",
+              "weekly"
+            ],
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Built-in weekly or monthly reset cadence"
+      },
+      "periodic_reset_days": {
+        "anyOf": [
+          {
+            "maximum": 365,
+            "minimum": 1,
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Custom reset cadence in days, from 1 through 365"
+      },
+      "type": {
+        "description": "Whether the limit measures cost or tokens",
+        "enum": [
+          "cost",
+          "tokens"
+        ],
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedInput schema / properties / users

Added value: +{
+  "description": "Existing user IDs to add",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

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

TDQS

A3.8/5.0

Behavior4/5

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

Annotations declare openWorldHint=true, idempotentHint=false, destructiveHint=false, covering the safety profile. The description adds genuinely useful behavioral context beyond the annotations: slug auto-generation from name when omitted, and that the response includes id, name and slug.

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 tight sentences, front-loaded with the core action and purpose, followed by the slug/return detail. No wasted words.

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 mutation with nested rate/usage-limit objects and an output schema, the description plus rich schema/annotations gives an agent enough to call it correctly. Slightly incomplete on guidance for the optional rate_limits/usage_limits setup, but those are well documented 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%, so all 8 parameters are documented there; the baseline is 3. The description adds a bit of value on the slug auto-generation rule but says nothing about the complex rate_limits/usage_limits or is_default semantics beyond what the schema already provides.

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?

States a specific verb ('create') and resource ('workspace') plus the isolation purpose (resources, API keys, team members), which clearly distinguishes it from get_workspace/update_workspace/delete_workspace. It doesn't explicitly name a sibling to prefer, but 'create' is inherently unambiguous.

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

Usage Guidelines3/5

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

Usage is implied by the verb – use this to make a new workspace – but there is no explicit when-to-use/when-not guidance or reference to alternatives like update_workspace or add_workspace_member for adding members after creation.

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

Deploy Server