Skip to main content
Glama

Change a style

adjust_style
DestructiveIdempotent

Change one of the linked account's saved styles in plain words, for example 'bigger yellow captions, no zooms' or 'open on the strongest line'. Saves it as the style's next version; every later video in that style follows it, and earlier versions are kept. Preserve operation_id on retries.

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": {
      "style_id": "<style_id>",
      "change": "<change>",
      "operation_id": "<operation_id>"
    },
    "name": "adjust_style"
  }
}

Input Schema

NameRequiredDescriptionDefault
changeYesThe change in the user's words, e.g. 'bigger yellow captions, no zooms'.
style_idYesOne of the user's saved styles (get_profile own_styles).
operation_idYesSame id retries run once.

Output Schema

NameRequiredDescriptionDefault
codeNo
costNo
errorNo
stateNo
statusNo
dry_runNo
messageNo
plan_idNo
style_idNo
video_idNo
availableNo
import_idNo
output_idNo
studio_urlNo
version_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / operation_id / pattern
      Removed value: -"^[a-zA-Z0-9_.:-]{1,100}$"
  2. Added
  3. Removed
  4. Changed1 schema field changed
    • changedInput schema / properties / operation_id / description
      Previous value: -"A retry with the same id runs once."New value: +"Same id retries run once."
  5. Changed1 schema field changed
    • changedInput schema / properties / style_id / description
      Previous value: -"One of the user's saved styles (own: true in browse_styles)."New value: +"One of the user's saved styles (get_profile own_styles)."
  6. Changed1 schema field changed
    • changedInput schema / properties / operation_id / description
      Previous value: -"The same id on a retry runs it once; a new id is a new request."New value: +"A retry with the same id runs once."
  7. Changed3 schema fields changed
    • addedInput schema / properties / change / description
      Added value: +"The change in the user's words, e.g. 'bigger yellow captions, no zooms'."
    • changedInput schema / properties / operation_id / description
      Previous value: -"A stable ID for this authorized request. Preserve it on retries. Use a new ID only for a deliberate new request."New value: +"The same id on a retry runs it once; a new id is a new request."
    • addedInput schema / properties / style_id / description
      Added value: +"One of the user's saved styles (own: true in browse_styles)."
  8. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "description": "Clypmint adjust_style result. Error results carry error; successful requests expose the identifiers and state available for the next step. Signed media stays in private metadata.",
      +  "properties": {
      +    "available": {
      +      "type": "boolean"
      +    },
      +    "code": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "cost": {
      +      "additionalProperties": true,
      +      "type": "object"
      +    },
      +    "dry_run": {
      +      "type": "boolean"
      +    },
      +    "error": {
      +      "type": "string"
      +    },
      +    "import_id": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "message": {
      +      "type": "string"
      +    },
      +    "output_id": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "plan_id": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "state": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "status": {
      +      "type": [
      +        "string",
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "studio_url": {
      +      "format": "uri",
      +      "type": "string"
      +    },
      +    "style_id": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "version_id": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "video_id": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  9. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that the edit is persisted as a new version, that every later video in that style inherits the change, and that earlier versions are retained — important nuance for a tool flagged destructiveHint=true. It also states the retry contract for operation_id, which annotations alone do not convey.

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?

Three front-loaded sentences with no filler, each carrying distinct information (intent, versioning side effects, retry rule). The inline examples partially duplicate the change parameter's schema description, a minor redundancy.

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 3-parameter mutation with full schema coverage and an output schema, the description supplies exactly what structured fields cannot: natural-language input expectations, versioning/propagation consequences, and retry semantics.

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%, so baseline is 3; the description adds meaning by stressing the change must be in the user's plain words with realistic phrasings, and by telling the caller to preserve operation_id across retries rather than merely restating the schema's 'same id retries run once'.

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?

States a specific verb and resource ('Change one of the linked account's saved styles') with concrete example changes, which lets an agent distinguish it from copy_style and browse_styles without opening a schema.

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?

Implies the use case — modify an existing saved style by describing the change in natural language — but gives no explicit when-not guidance or named alternative (e.g., when to use copy_style or browse_styles instead).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources