Skip to main content
Glama

adb_market_export

Export a local workflow with marketplace metadata into a shareable JSON file containing name, description, version, author, and tags for registry submission.

Instructions

Export a local workflow with marketplace metadata for sharing. Produces a JSON file with name, description, version, author, and tags suitable for submission to the marketplace registry.

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": {
      "workflow": "<workflow>"
    },
    "name": "adb_market_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoTags for discovery (e.g., ['testing', 'diagnostics'])
authorNoAuthor name to include in metadata
versionNoVersion string (semver-style, e.g., '1.2.3'). Defaults to '1.0.0' if omitted. Increment when publishing an updated workflow so registry consumers can detect changes.1.0.0
workflowYesName of the local workflow to export (from adb_workflow_list)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed2 schema fields changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / version / description
      Previous value: -"Version string"New value: +"Version string (semver-style, e.g., '1.2.3'). Defaults to '1.0.0' if omitted. Increment when publishing an updated workflow so registry consumers can detect changes."
  3. First observedv1.1.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the output shape (a JSON file containing name, description, version, author, tags), but says nothing about where the file is written, whether it overwrites an existing export, or what happens if the named workflow does not exist.

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?

Two tight sentences, front-loaded with the action and followed by the artifact produced. No filler and nothing an agent must scroll past to find the core purpose.

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 four-parameter export tool with no annotations and no output schema, the description covers purpose and the resulting file's contents. It is missing the practical details an agent needs to act on the result, namely the output location and whether the workflow must already exist locally.

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 coverage is 100%, so all four parameters are already documented in the schema, and the description largely restates that field list. It also mentions a 'description' field that has no corresponding parameter in the schema, which adds slight ambiguity rather than meaning.

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 and resource ('Export a local workflow with marketplace metadata') and states the artifact produced. It is distinguishable from siblings like adb_market_install or adb_market_search, though it never names them explicitly to reinforce the export-vs-install distinction.

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?

Usage is implied by 'for sharing' and 'suitable for submission to the marketplace registry', which signals the pre-publish step. There is no explicit when-to-use/when-not guidance and no pointer to the complementary tools (adb_workflow_validate, adb_market_install) an agent would pair this with.

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