Skip to main content
Glama
Sign In

LinkedIn MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

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 LinkedIn it serves these actions: Create post, Comment on post, Send message, Send connection invitation, Search people, Search companies, List connections, Read conversations.

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

NameRequiredDescriptionDefault
appNoLeave 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.
urlNoA public http or https address, e.g. https://example.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, so the description's added value is elsewhere: it discloses that this is an authenticated real-browser session, that the user's existing tabs are preserved, and — critically, since there is no output schema — that it returns the in-view elements and text using the 'same numbers' as other tools. It does not explain what happens with a repeated call against an already-open browser, which is why non-idempotent is flagged but not fully elaborated.

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

Conciseness5/5

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

Purpose, sequencing rule, tab behavior, and return payload are front-loaded in three dense sentences with no filler. The trailing LinkedIn action list is slightly listy but earns its place by telling the agent which site-level actions this browser session can serve.

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?

With only two optional parameters, full schema coverage, and annotations covering the safety profile, the description supplies the missing piece — what the call returns — so an agent can chain into click/find without guessing. The only gap is the lack of any guidance on repeated invocations given the non-idempotent hint.

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%, so both `app` and `url` are already documented in the schema, including the guidance to omit `app`. The description adds only the tab-routing behavior for `url` and says nothing about `app`, so it does not meaningfully exceed the schema baseline.

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?

States a specific verb and resource ('Starts the user's Cloud Browser ... and opens `url`') and adds qualifying detail that separates it from siblings: it is a real Chrome session where the user is already signed in, and it is the entry point ('Call it first'), unlike navigate/click/read which act on an already-open browser.

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' is an explicit sequencing directive, and the note that the URL lands in the site's existing tab or a new tab clarifies the default behavior an agent should expect. It stops short of naming a when-not-to-use case or explicitly contrasting with cotlet_browser_navigate, but the ordering rule covers the main selection decision.

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

All LinkedIn MCP Server and API by Cotlet toolsInspect
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