Skip to main content
Glama
bruhsb
by bruhsb

paperclip_update_secret

DestructiveIdempotent

Update a secret's metadata (name, description, external reference) without changing its value. Requires board-level API key.

Instructions

⚠ Board-only: Update secret metadata (name, description, externalRef). To rotate the secret value, use paperclip_rotate_secret.

Args:

  • secretId: string — Secret UUID

  • name: string (optional) — New secret name

  • description: string | null (optional) — New description (null to clear)

  • externalRef: string | null (optional) — New external reference (null to clear)

Returns: Updated secret metadata: id, companyId, name, provider, externalRef, latestVersion, description, timestamps. Value is never returned.

Examples:

  • Use when: renaming a secret or updating its description or external reference without changing its value

  • Don't use when: you need to change the secret value — the value field is not accepted here; use paperclip_rotate_secret instead

Error Handling:

  • 404: secret not found → verify secretId with paperclip_list_secrets

  • 401: authentication failed → check PAPERCLIP_API_KEY

  • 403: permission denied → this tool requires a board (human-user) API key

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
secretIdYesSecret UUID
nameNoNew secret name
descriptionNoNew description (null to clear)
externalRefNoNew external reference (null to clear)
Behavior5/5

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

Annotations already indicate destructive and idempotent behavior. Description adds significant context: board-only requirement, return format (value never returned), error handling. 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with sections for args, returns, examples, error handling. Front-loaded with key caveats. While detailed, every sentence serves a purpose; slight room for trimming but not excessive.

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?

Comprehensive for a metadata update tool: covers purpose, usage boundaries, parameter details, return shape (despite no output schema), and error handling. Fully prepares the agent for correct invocation.

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 covers 100% with descriptions. Description restates parameter roles and notes null clears, but adds minimal new semantics beyond schema. Baseline 3 is appropriate.

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 clearly states it updates secret metadata (name, description, externalRef) and explicitly distinguishes from rotating the secret value. The verb 'update' and resource 'secret metadata' are specific, and it differentiates from the sibling tool paperclip_rotate_secret.

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?

Provides explicit when-to-use (renaming, updating description/reference) and when-not-to-use (changing value, directing to paperclip_rotate_secret). Also includes error handling guidance for 404, 401, 403 with actionable next steps.

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/bruhsb/paperclip-mcp'

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