Skip to main content
Glama
Sign In
ZennoBrowser MCP Server

ZennoBrowser MCP Server

Official
by ZennoLab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Creates a new preset.

create_preset

Create a new cloud-based preset to group extensions and bookmarks, then assign it to browser profiles for organized management.

Instructions

Creates a new preset. Presets are used to group extensions, bookmarks, manage them together and assign them to profiles. All presets are cloud-based.

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

Input Schema

NameRequiredDescriptionDefault
nameYesPreset name
iconNameNoPreset icon name. Example: "like", "dislike", "star", "ai", etc.
workspaceIdNoWorkspace identifier. -1 means the default workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already disclose the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false), so the bar is lower. The description adds one useful behavioral fact — 'All presets are cloud-based' — but says nothing about required auth, whether the new preset is auto-assigned to a profile, or what the response contains.

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?

Three short sentences with the action front-loaded and no filler. The middle sentence is slightly run-on ('group extensions, bookmarks, manage them together and assign them to profiles'), but overall it is tight and earns its space.

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?

For a mutation tool with full annotation coverage, 100% schema coverage, and no output schema, the description supplies adequate domain context about what presets are and that they live in the cloud. It stops short of explaining creation side effects or profile assignment behavior, which would have made it fully complete.

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 name, iconName, and workspaceId are already documented by the schema itself. The description adds no additional parameter meaning — the 'cloud-based' note does not clarify workspaceId semantics — so the baseline of 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 first sentence states a specific verb+resource ('Creates a new preset') and the following sentences explain what a preset actually is, which helps an agent understand the object being created. Differentiation from siblings is implicit rather than stated; there is only one create_preset among the siblings, but the description never contrasts it with get_presets or delete_preset.

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 explains the concept of presets (group extensions/bookmarks, assign to profiles) which implies the usage context, but gives no explicit when-to-use or when-not guidance and names no alternatives. An agent can infer it is the creation entry point for the preset family, but nothing is spelled out.

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