Skip to main content
Glama
MCP Prompts Server

MCP Prompts Server

by sparesparrow

Update a prompt

update_prompt
Destructive

Change fields of an existing prompt, keep omitted values, and increment its version; use it to revise content, metadata, tags, variables, or settings.

Instructions

Change fields of an existing prompt; fields left out of updates keep their value, and the version goes up. Replaces the previous values, which are not kept.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>",
      "updates": "<updates>"
    },
    "name": "update_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPrompt ID
updatesYesThe fields to change; fields left out keep their value

Output Schema

NameRequiredDescriptionDefault
idYes
nameYes
versionYes
persistedYesTrue when the change was saved to the state directory, false when it is in memory only

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv4.1.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / id / minLength
      Added value: +1
    • addedInput schema / properties / updates / additionalProperties
      Added value: +false
    • addedInput schema / properties / updates / description
      Added value: +"The fields to change; fields left out keep their value"
    • addedInput schema / properties / updates / properties / category
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / updates / properties / content / maxLength
      Added value: +1000000
    • addedInput schema / properties / updates / properties / content / minLength
      Added value: +1
    • addedInput schema / properties / updates / properties / description
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / updates / properties / name / minLength
      Added value: +1
    • changedInput schema / properties / updates / properties / variables / items / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "properties": {
      -      "description": {
      -        "type": "string"
      -      },
      -      "name": {
      -        "type": "string"
      -      },
      -      "required": {
      -        "default": true,
      -        "type": "boolean"
      -      },
      -      "type": {
      -        "default": "string",
      -        "enum": [
      -          "string",
      -          "number",
      -          "boolean"
      -        ],
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "name"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  {
      +    "properties": {
      +      "description": {
      +        "type": "string"
      +      },
      +      "name": {
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "required": {
      +        "default": true,
      +        "type": "boolean"
      +      },
      +      "type": {
      +        "default": "string",
      +        "enum": [
      +          "string",
      +          "number",
      +          "boolean"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "name"
      +    ],
      +    "type": "object"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "id": {
      +      "type": "string"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "persisted": {
      +      "description": "True when the change was saved to the state directory, false when it is in memory only",
      +      "type": "boolean"
      +    },
      +    "version": {
      +      "type": [
      +        "number",
      +        "string"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "id",
      +    "name",
      +    "version",
      +    "persisted"
      +  ],
      +  "type": "object"
      +}
  2. Changed6 schema fields changedv4.0.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / updates / additionalProperties
      Removed value: -false
    • removedInput schema / properties / updates / properties / isTemplate / default
      Removed value: -false
    • addedInput schema / properties / updates / properties / metadata / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / updates / properties / tags / default
      Removed value: -[]
    • changedInput schema / properties / updates / properties / variables / items / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "description": {
      -        "type": "string"
      -      },
      -      "name": {
      -        "type": "string"
      -      },
      -      "required": {
      -        "default": true,
      -        "type": "boolean"
      -      },
      -      "type": {
      -        "default": "string",
      -        "enum": [
      -          "string",
      -          "number",
      -          "boolean"
      -        ],
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "name"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "properties": {
      +      "description": {
      +        "type": "string"
      +      },
      +      "name": {
      +        "type": "string"
      +      },
      +      "required": {
      +        "default": true,
      +        "type": "boolean"
      +      },
      +      "type": {
      +        "default": "string",
      +        "enum": [
      +          "string",
      +          "number",
      +          "boolean"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "name"
      +    ],
      +    "type": "object"
      +  }
      +]
  3. First observedv4.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds two non-obvious behaviors beyond them: omitted fields are preserved, and the version increments on each call. It also explicitly warns that previous values are overwritten and not retained, which explains concretely what is destroyed.

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?

Two tight clauses, front-loaded with the core action, and no filler. The second sentence slightly overlaps the first's partial-update framing (both convey that prior state is replaced), but the warning about irreversibility justifies its presence.

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?

With an output schema present and full schema documentation, the description only needs to explain mutation semantics, which it does, including the version bump and non-retention of old values. Minor gaps remain around error behavior for an unknown `id` and whether version increments have downstream side effects.

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%, including an inline description on `updates` that already states 'fields left out keep their value'. The description restates that same semantic rather than adding new meaning, so the baseline 3 applies.

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 and resource: 'Change fields of an existing prompt', plus the partial-update semantics. It is clearly a mutation on an existing entity, distinguishing it in spirit from add_prompt/delete_prompt, though it never names those siblings explicitly.

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 only implied: 'existing prompt' and 'fields left out keep their value' suggest partial edits rather than creation or full replacement. There is no explicit when-to-use/when-not-to-use guidance and no mention of alternatives such as apply_template or delete_prompt.

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