Skip to main content
Glama

Export workflow pack

export_workflow_pack
Read-onlyIdempotent

Export a read-only JSON pack of personas, tools, turnstiles, and stacks from a workspace for backup or transfer without writing to Studio, then reimport with import_studio_pack.

Instructions

Export a read-only workflow pack of personas, tools, turnstiles and stacks. Does not write Studio. Use import_studio_pack to bring a pack back in. Returns JSON pack.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "export_workflow_pack"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum rows per kind. Integer from 1 to 500. Default 200.
includeNoOptional entity kinds to include, such as personas or tools. Omit for the default set.
workspaceNoOptional Studio workspace name, slug or id from list_workspaces. Omit for the active workspace.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv6.3.0
    • addedInput schema / properties / workspace
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Optional Studio workspace name, slug or id from list_workspaces. Omit for the active workspace.",
      +  "title": "Workspace"
      +}
  2. Changed2 schema fields changedv6.2.1
    • addedInput schema / properties / include / description
      Added value: +"Optional entity kinds to include, such as personas or tools. Omit for the default set."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum rows per kind. Integer from 1 to 500. Default 200."
  3. Addedv6.1.5

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description reinforces non-mutation ('Does not write Studio') and notes the JSON return, but adds little beyond what annotations and the output schema already provide.

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

Conciseness5/5

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

Three short sentences, front-loaded with the core action and contents, then the non-mutation constraint and the alternative. No wasted wording.

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 rich annotations, a full output schema and 100% parameter coverage, the description supplies what is needed: what is exported, that it is read-only, and the inverse operation. Minor omission of workspace/limit scoping is covered by the schema.

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%, with limit, include and workspace fully documented in the schema. The description adds no parameter-level meaning, so the baseline 3 applies.

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 (Export) and resource (workflow pack) plus the exact contents (personas, tools, turnstiles, stacks), and explicitly contrasts with import_studio_pack. An agent can distinguish it from siblings without opening the schema.

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

Usage Guidelines4/5

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

Gives clear context ('Does not write Studio') and names the inverse tool import_studio_pack for bringing a pack back in. It does not address when to prefer this over export_tool_config, but the usage context is otherwise unambiguous.

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