JazzHR 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 JazzHR it serves these actions: List candidates, Move candidate to a workflow stage, Bulk change candidate status, Email candidate, Add candidate note, Create task, Set job status, Create job.

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

A3.9/5.0

Behavior4/5

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

Beyond the annotations, it discloses meaningful behavior: the browser is the user's real signed-in Chrome (auth context), the existing tab is reused so the user's own tabs stay, and the call returns the in-view elements and text. That is more than readOnlyHint/openWorldHint convey on their own. It leaves unexplained why the call is not idempotent (repeated calls, browser already running).

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 and mostly economical: the core action, the ordering instruction, and the tab behavior come first. The trailing JazzHR action list is the weakest part, since it enumerates sibling `jazzhr_*` tool capabilities rather than anything specific to opening the browser, and "with the same numbers" is vague.

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?

There is no output schema, and the description does sketch what comes back (in-view elements and text), which is what an agent needs to chain calls. Combined with annotations covering safety and open-world access, the definition is close to complete; the main missing piece is behavior when the browser session is already open.

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 `url` and `app` are already documented in the schema. The description adds only the routing behavior of `url` (existing tab vs new tab) and says nothing about `app`. Baseline 3 is appropriate when the schema carries the parameter semantics.

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?

States a specific verb and resource: starts the user's Cloud Browser (a real signed-in Chrome) and opens `url`. That is unambiguous. It does not, however, distinguish itself from the sibling `cotlet_browser_navigate`, which sounds like it opens URLs too, so an agent must guess between the two.

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, and the description explains where the URL lands (existing tab, else new tab). It never states when NOT to use it, particularly versus `cotlet_browser_navigate` or `cotlet_browser_read`.

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

All JazzHR 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?