Skip to main content
Glama

studio_bundle

Export a portable project manifest and original reference assets to a local folder for backup, migration, or offline review; account credentials are excluded.

Instructions

Export portable canonical project manifest and original reference assets to a local folder; does not include account credentials.

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": {
      "projectId": "<projectId>",
      "outputDir": "<outputDir>"
    },
    "name": "studio_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
outputDirYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and it discloses only one negative trait (credentials excluded). It does not say whether it writes files to disk, whether outputDir must exist or is created, whether existing folder contents are overwritten or deleted, or what auth/plan requirements apply to a filesystem-writing operation.

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?

A single front-loaded sentence with the core action first and the scope exclusion attached; there is no filler or repetition.

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?

The tool is simple (two params, no output schema, no nested objects), so the description doesn't need to explain return values. However, for a tool that writes to a user-supplied directory it omits both parameter meaning and filesystem side effects, leaving the definition only marginally adequate.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must supply the meaning of projectId and outputDir, yet it never mentions either parameter. The names are largely self-explanatory, but nothing clarifies path formatting, relative vs absolute paths, or identifier format, which is a real gap for a 2-param tool with no schema docs.

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 gives a specific verb (export) and precise resources (canonical project manifest plus original reference assets) with the destination named (local folder). It's clear what the tool produces, though it doesn't distinguish itself from the sibling studio_import_project or explain how the bundle differs from other studio_* outputs.

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 no guidance on when to use this versus alternatives such as studio_sync_plan or studio_library, and no prerequisites (project must exist, permissions, disk space) are stated. The only scoping statement, 'does not include account credentials,' describes bundle contents rather than a usage condition.

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