Skip to main content
Glama
Sign In
Mochi

Mochi

by DevZonayed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

browser_playbook_export

Export playbooks and their screenshots into a single JSON bundle for sharing across projects or teams. Simplifies collaboration and reuse of browser automation workflows.

Instructions

Export one or more playbooks (and their screenshots) to a single JSON bundle file. Useful for sharing across projects or teams.

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": "browser_playbook_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsNo
originNo
tagNo
outputPathNo
stripSecretsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/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 full burden. It does not disclose side effects (e.g., whether export deletes playbooks), permissions required, or the effect of the `stripSecrets` parameter. The description is too brief to convey behavioral traits.

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?

The description consists of two concise sentences. The first defines the action and output; the second adds context. It is front-loaded and contains no redundant words, though it could be slightly expanded without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 5 parameters (none documented), no output schema, and no parameter descriptions, the description is insufficient for correct invocation. An agent would not know how to use parameters like `origin` or `stripSecrets` or what the output bundle contains.

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

Parameters1/5

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

Schema description coverage is 0%, and the description adds no information about any of the 5 parameters (ids, origin, tag, outputPath, stripSecrets). It only hints at 'one or more playbooks' but does not explain which parameter controls selection or how to specify paths.

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?

The description clearly states the verb 'Export', the resource 'one or more playbooks (and their screenshots)', and the output format 'single JSON bundle file'. It distinguishes from sibling tools like browser_playbook_list or browser_playbook_get by specifying bundling and screenshots.

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 description mentions 'Useful for sharing across projects or teams', giving a use case. However, it does not explicitly state when not to use it or suggest alternative tools (e.g., browser_playbook_get for a single playbook, or browser_playbook_import for the reverse).

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