Retrieve saved browser workflows, filtered by origin or show all.
List saved workflows. Pass origin to filter (defaults to current).
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": "browser_workflow_list"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| origin | No | ||
| all | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description fully carries the burden of behavioral disclosure. It only states 'List saved workflows' which implies a read operation, but does not disclose potential side effects, permissions, return format, pagination, or any error conditions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very concise at one sentence, front-loading the purpose and key parameter guidance. It is appropriately sized for a simple list function, though a bit more detail on the second parameter would not hurt.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, no annotations, and low schema coverage, the description leaves significant gaps. It does not explain return structure, pagination, or the behavior of the 'all' parameter, making it incomplete for a thorough understanding.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description explains the 'origin' parameter (filter, defaults to current) adding value beyond the bare schema. However, the 'all' parameter is left unexplained, and schema coverage is 0%, so the description only partially compensates.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'List saved workflows', providing a specific verb and resource. While it does not explicitly differentiate from sibling tools like 'browser_playbook_list', the name and context make it obvious this is for workflows.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description advises to pass 'origin' for filtering and mentions the default behavior, which gives basic usage guidance. However, it does not explain when to use this tool over alternatives, nor does it mention the 'all' parameter or any prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.