Brandfolder MCP Server and API by Cotlet

Cotlet: how to work in an app

cotlet_app_guide

Read-onlyIdempotent

How to work in an app by clicking in the user's Cloud Browser with Cotlet's browser tools: which browser to use for this workspace and the sign-in link, the method step by step, the app's screens, menus and actions, notes, and the app's dedicated tools when Cotlet has them. Call it before the first browser step in an app. Works for any web app; one outside Cotlet's catalog gets the general method. Free, no browser session. For Brandfolder it covers 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_app_guide"
  }
}

Input Schema

Name	Required	Description	Default
`app`	No	The app's name or Cotlet slug. Default: Brandfolder.
`task`	No	What the user wants done in the app, in their words.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover read-only/idempotent/no-destruction, so the description's added value is the "Free, no browser session" cost note and the catalog-vs-outside fallback behavior – both genuinely useful beyond structured data. It doesn't describe how large the returned guide is or whether it is cached, but nothing important is missing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The main sentence is a long comma-separated inventory that is hard to scan; the actionable trigger ("Call it before the first browser step") is buried mid-paragraph. The Brandfolder action list at the end is useful but bulky and could be compressed ("covers search/get/add/tag/collect/share/delete actions").

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?

No output schema exists, and the description does enumerate what the guide contains, which is the key thing an agent needs to decide whether to call it. Combined with the cost note and the catalog fallback, an agent has enough to invoke it correctly.

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% and the schema already documents name-or-slug, the 120-char cap, the default of Brandfolder, and the task field. The description only reinforces that any web app works and outside-catalog apps fall back to the general method – a small addition, so baseline 3 is right.

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 states concretely what the tool returns: which browser and sign-in link for the workspace, the step-by-step method, screens, menus, actions, notes, and any dedicated Cotlet tools. That distinguishes it from siblings like cotlet_apps (catalog listing) and the cotlet_browser_* primitives, though the opening clause is a rambling run-on rather than a crisp verb+resource statement.

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?

Gives an explicit trigger: "Call it before the first browser step in an app." It also explains the fallback for apps outside the catalog (general method). No explicit when-not-to-use is given, and it doesn't say whether to re-call on subsequent sessions in the same app.

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?