Skip to main content
Glama

adb_market_install

Download and install a workflow from the marketplace into your local workflows directory so you can run it immediately with adb_workflow_run. Use the force option to overwrite an existing workflow.

Instructions

Download and install a workflow from the marketplace. Saves to the workflows directory for immediate use with adb_workflow_run.

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

Input Schema

NameRequiredDescriptionDefault
nameYesWorkflow name from the marketplace
forceNoOverwrite if a workflow with this name already exists locally

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. Changed1 schema field changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.1.1

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden for a tool that mutates local disk state. It does disclose the destination ('workflows directory') and that force controls overwriting, which is useful, but it omits what happens by default when a workflow already exists (error vs. skip), whether anything needs network access or auth, and whether overwriting is recoverable.

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?

Two short sentences, front-loaded with the action and followed by the practical consequence. Nothing is redundant, though the second sentence could more precisely say why adb_workflow_run matters rather than merely naming it.

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 two-parameter tool with full schema coverage and no output schema, this is close to sufficient: the agent knows the source, destination, and next step. What is missing is conflict behavior when force is false and any indication of what the call returns on success or failure.

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%, so both 'name' and 'force' are already documented in the schema, including the overwrite semantics. The description adds the useful fact that the install lands in the workflows directory, but contributes no new detail about parameter format or validation; baseline 3 applies.

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 names a specific verb pair and resource: 'Download and install a workflow from the marketplace.' That is clear enough to separate it from adb_market_search (find) and adb_workflow_run (execute). It does not, however, distinguish it from the similarly named adb_registry_install, which an agent could easily confuse for the same operation.

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?

The second sentence ('for immediate use with adb_workflow_run') implies the follow-up workflow and therefore the reason to call this tool. There is no explicit when-to-use versus adb_market_search or adb_registry_install, and no stated preconditions such as needing a known workflow name.

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