Skip to main content
Glama
Sign In
Bannerbear MCP Server

Bannerbear MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Update workflow

update_workflow
Destructive

Update an existing Bannerbear workflow via UID, modifying steps, inputs, tags, and name. Requires explicit confirmation before changes apply.

Instructions

PATCH /v5/workflows/{uid}. Current Bannerbear V5 operation; provider scopes, locks and credits apply. Mandatory confirmation before provider execution; one submission only.

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": {
      "uid": "<uid>"
    },
    "name": "update_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYes
accountNoExact private workspace profile label; no fallback to another profile key.
confirmNoMust be true for this exact requested render, upload, edit, install or delete.
payloadNoComplete current native JSON body. Use payload or payload_file exclusively.
payload_fileNoRegular non-symlink local JSON file, at most 1 MiB.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is partly covered. The description adds genuinely new context beyond that: provider scopes/locks/credits apply, confirmation is mandatory before execution, and it is a one-submission operation (reinforcing non-idempotence and warning against retries). That is real behavioral value, though it never states what the destructive update actually replaces.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

It is tight and front-loaded, but the terseness comes at the cost of under-specification rather than efficiency. Two of the three clauses (scopes/locks/credits, confirmation) are dense jargon that would benefit from one clarifying phrase.

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 destructive, non-idempotent mutation with a nested payload and no output schema, the description covers execution mechanics (confirmation, single submission) but omits the key semantic that the payload is a complete replacement body whose omitted fields are dropped. Given schema-side coverage and the destructive annotation, this is minimally adequate rather than complete.

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 80%, so the schema already documents account, confirm, payload and payload_file (including the 'payload or payload_file exclusively' note). The description adds nothing about parameter meaning or interaction beyond echoing {uid} in the path. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the HTTP method and path (PATCH /v5/workflows/{uid}), which conveys a mutating operation on the workflows resource, but it never says in semantic terms what is being updated (name, tags, steps). It does no sibling differentiation against update_image_template, update_webhook, or update_instant_url, which share the same verb.

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?

There is a prerequisite hint ('Mandatory confirmation before provider execution'), but no guidance on when to reach for update_workflow versus create_workflow or get_workflow, and no statement of when-not-to-use. 'Current Bannerbear V5 operation' implies a version constraint but is not actionable as routing guidance.

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