Feedly 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 Feedly it serves these actions: List feeds, List articles, Search articles, Save article to Board, Mark articles as read, Follow source.

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?

Annotations already cover safety (readOnly/openWorld/non-destructive), but the description adds genuinely new behavior: the target URL lands in the site's open tab else a new tab, existing user tabs are preserved, and the response is the post-load page's in-view elements and text 'with the same numbers'. That response-shape disclosure matters because no output schema exists. It stops short of stating session/auth prerequisites or failure modes.

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 'call it first' instruction, and each sentence carries information about behavior or downstream use. The trailing Feedly action list is the weakest part — it reads as an inventory of sibling tools rather than something needed to invoke this one.

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 launch tool with no output schema, the description covers initiation, tab placement, and what the returned page content looks like. The main omission is how this relates to `cotlet_browser_navigate`/`cotlet_browser_read` once the session is 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 coverage is 100%, so both `url` and `app` are already documented, including the conditional 'leave it out' rule for `app`. The description adds only the framing that this is the user's signed-in browser; it restates rather than extends parameter meaning, so the baseline 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?

Specific verb and resource: 'Starts the user's Cloud Browser ... and opens `url`', with a concrete definition of what the Cloud Browser is (a real Chrome where the user is signed in). It does not distinguish itself from the sibling `cotlet_browser_navigate`, which an agent would reasonably compare it to, so it falls short of a 5.

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 ordering guidance, and the note that it opens in the site's existing tab or a new one frames expected context. There is no when-not guidance and no explicit handoff to `cotlet_browser_navigate` for mid-session navigation, leaving a real ambiguity unresolved.

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

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