Skip to main content
Glama

update_secret_reference

DestructiveIdempotent

Update a stored secret reference by changing its name, path, tags, description, workspace access, or merging new authentication credentials into existing configurations.

Instructions

Update at least one selected field on a Secret Reference. auth_config is merged into the existing manager-specific configuration. allowed_workspaces replaces all workspace mappings and sets allow_all_workspaces=false; allow_all_workspaces=true removes workspace-specific mappings. Credential values are sent to Portkey and exposed to the MCP transcript.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSecret Reference UUID or slug
nameNoNew human-readable name
tagsNoReplacement string key-value tags, or null to clear them
secret_keyNoNew key within a structured secret, or null to use the whole value
auth_configNoProvide at least one changed authentication field to merge into the existing configuration; choose one AWS, Azure, or HashiCorp field family and do not mix families
descriptionNoNew description, or null to clear it
secret_pathNoNew path of the secret in the external secret manager
allowed_workspacesNoReplacement list of workspace UUIDs or slugs allowed to use this reference; supplying it sets allow_all_workspaces=false
allow_all_workspacesNoWhether every workspace may use this reference; cannot be true with allowed_workspaces

Output Schema

TableJSON 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. Dates show when Glama detected each change.

  1. Addedv0.5.0

TDQS

A4.4/5.0
Behavior4/5

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

Adds value beyond annotations by detailing that auth_config is merged, allowed_workspaces replaces mappings, and credential values are exposed to transcript. No contradiction with annotations.

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 efficient sentences: purpose, key behavioral details, security note. Front-loaded with action, 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?

Covers critical merge/replace behaviors and credential exposure. With output schema present, return value explanation is unnecessary. Minor gap: no prerequisites or error conditions.

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 coverage is 100%, baseline 3. Description adds meaning by specifying merge behavior for auth_config and replacement logic for allowed_workspaces, enhancing schema 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 clearly states 'Update at least one selected field on a Secret Reference', specifying verb and resource. Differentiates from sibling create/delete/get/list by emphasizing partial update.

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?

Description explains merging vs replacing behavior for auth_config and allowed_workspaces, providing clear context for use. Lacks explicit when-not to use, but siblings are distinct.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CodesWhat/portkey-admin-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server