portkey-admin-mcp

update_config

Update a configuration by slug, modifying routing, cache, retry, or status fields. Each call creates a new version, preserving earlier ones for recovery, and changes apply immediately to all linked API keys and prompts.

Instructions

Update a config by slug; every call creates a new config version rather than overwriting, so earlier versions stay recoverable via list_config_versions. Only provided fields change: name, status, and all routing/cache/retry settings (cache_mode, cache_max_age, retry_attempts, retry_on_status_codes, strategy_mode, targets) are editable, while the slug stays fixed. Changes apply immediately to every API key and prompt referencing the config. Returns the update acknowledgement and new version_id.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	New name for the configuration
`slug`	Yes	Configuration slug to update
`status`	No	Configuration status
`targets`	No	Array of target providers
`cache_mode`	No	Cache mode: 'simple' or 'semantic'
`cache_max_age`	No	Cache max age in seconds
`strategy_mode`	No	Routing strategy
`retry_attempts`	No	Number of retry attempts (1-5)
`retry_on_status_codes`	No	HTTP status codes to retry on

Output Schema

TableJSON 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 changedAug 9, 2026
- addedInput schema / properties / targets / items / properties / provider / description
```
Added value: +"Provider slug to route requests to"
```
- addedInput schema / properties / targets / items / properties / virtual_key / description
```
Added value: +"Virtual key slug to use for this routing target"
```
Addedv1.0.1May 7, 2026
RemovedMay 1, 2026
First observedJan 1, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only mark readiness and idempotency, so the description carries the burden and does it well. It discloses versioned writes instead of overwrites, recoverability via list_config_versions, immediate propagation to all API keys/prompts, and the returned version_id, all of which materially affect how an agent should reason about repeated calls.

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?

Three sentences with no filler: purpose and key caveat first, then editable vs fixed fields, then impact and return value. Every sentence earns its place.

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 9-parameter mutation tool, the description covers the important context the schema and annotations cannot: versioning behavior, immediate global effect, slug immutability, and the version_id return. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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; the description adds value beyond it by giving patch semantics ('Only provided fields change'), marking the slug as fixed, and grouping the editable routing/cache/retry parameters. It does not need to repeat per-parameter descriptions.

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?

Description names a specific verb and resource: update a config by slug, and immediately differentiates the operation from overwrite-style updates by stating every call creates a new config version. This distinguishes it from sibling tools like create_config, delete_config, and list_config_versions without needing the schema.

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?

Clear context is provided: update by slug, only provided fields change, and the slug stays fixed, implying use a different creation path if a new slug is needed. It does not explicitly name create_config or state when not to call it, but the partial-update and versioning semantics effectively route the agent.

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

Deploy Server