Brandfolder MCP Server and API by Cotlet

Open the browser

cotlet_browser_open

Read-only

Starts the user's Cloud Browser (a real Chrome on Cotlet, where the user is signed in to their sites) and opens url. Call it first. The URL goes to the site's open tab, else to a new tab, so the user's own tabs stay. Answers the page after it: the elements and text in view, with the same numbers. In Brandfolder it serves these actions: Search assets, Get asset, Add asset from URL, Tag asset, Set custom field, Create collection, Add asset to collection, Create share link, Delete asset.

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

Input Schema

Name	Required	Description	Default
`app`	No	Leave it out: the step runs in the user's web browser. Only when cotlet_app_guide names an app's own Cloud Browser, that app's slug, e.g. milanote.
`url`	No	A public http or https address, e.g. https://example.com.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly/openWorld/non-idempotent/non-destructive, so the bar is lower, yet the description adds real context: the URL reuses the site's existing tab or opens a new one and the user's own tabs are preserved. It also sketches the return payload ("the elements and text in view") absent an output schema, though "with the same numbers" is opaque.

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?

Front-loaded with the action and the ordering instruction, then tab behavior and the return shape in tight sentences. The trailing Brandfolder action list is tangential to opening a browser and reads as promotional bulk rather than invocation guidance.

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 two-parameter, no-output-schema tool, the description covers session context, tab side effects, ordering, and a rough return shape. The only gap is not contrasting with cotlet_browser_navigate and the vague "same numbers" reference to page element numbering.

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 `app` and `url` are already fully documented in the schema, including the guidance to omit `app`. The description adds only tab-routing behavior for the URL, not new meaning about parameter values or formats.

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?

Specific verb and resource: "Starts the user's Cloud Browser ... and opens `url`", plus concrete context that it is a real Chrome session where the user is signed in. "Call it first" separates it from the downstream browser siblings like cotlet_browser_click or cotlet_browser_read.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Call it first" gives explicit sequencing guidance relative to the other browser tools, which is the core when-to-use signal. It does not, however, contrast itself with cotlet_browser_navigate, a sibling whose name suggests overlapping behavior, so the exclusion set is incomplete.

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

All Brandfolder MCP Server and API by Cotlet tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?