Skip to main content
Glama
Sign In
Storyblok MCP Server

Storyblok MCP Server

by Kiran1689
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

update_branch

Modify an existing branch in a Storyblok space via the Management API. Update branch name, source branch, preview URL, or position to streamline pipeline management.

Instructions

    Updates an existing branch (pipeline) in a Storyblok space via the Management API.

    - branch_id: Numeric ID of the branch to update.
    Optional fields:
      - name: New branch name
      - source_id: Set/clear source branch (clone origin)
      - url: Preview URL
      - position: Position ordering number

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": {
      "branch_id": "<branch_id>"
    },
    "name": "update_branch"
  }
}

Input Schema

NameRequiredDescriptionDefault
branch_idYes
nameNo
positionNo
source_idNo
urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only states it's an update operation via the Management API. It lacks details on permissions required, whether changes are reversible, rate limits, or what happens to unspecified fields, which are critical for a mutation tool.

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?

The description is front-loaded with the core purpose, followed by a bulleted list of parameters. It's efficient with minimal waste, though the bullet formatting could be slightly more structured for readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with 5 parameters, no annotations, and no output schema, the description covers parameters well but lacks behavioral context and output details. It's partially complete but leaves gaps in understanding the tool's full impact and response.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description compensates by clearly explaining all 5 parameters: branch_id as required numeric ID, and optional fields (name, source_id, url, position) with brief semantics. This adds significant value beyond the bare schema.

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?

The description clearly states the action ('Updates') and resource ('an existing branch (pipeline) in a Storyblok space'), specifying it uses the Management API. It distinguishes from siblings like 'create_branch' by focusing on updates, but doesn't explicitly contrast with other update tools like 'update_space' or 'update_story'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites, such as needing a branch_id, or compare with other update tools in the sibling list, leaving the agent to infer usage context.

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

Deploy Server

Other Tools

Related Tools