bulk_stop_threadStops multiple execution threads at once by passing an array of thread tokens, with an optional workspace ID. Use it to halt parallel browser tasks and free resources.
This method stops multiple execution threads.
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | Target execution thread tokens Example: ["uuid1", "uuid2"]. | |
| workspaceId | No | Workspace identifier. -1 means the default workspace. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say what happens to associated browser instances or profiles, whether partial failures are possible, or whether the operation is reversible.
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?
A single front-loaded sentence with no waste, but also no added substance. Sized appropriately for a simple bulk operation.
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?
For a destructive bulk mutation with no output schema, the description is too thin. It omits what a stopped thread means for any running browser instance, error behavior on invalid tokens, and whether the action can be undone.
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?
Schema description coverage is 100%, so both the thread-token array and the workspaceId default are already documented in the schema. The description adds no additional meaning about token format or batching limits; baseline 3 applies.
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?
States a specific verb and resource ('stops multiple execution threads'), and the plural 'multiple' implicitly distinguishes it from the sibling stop_thread. It does not, however, explicitly name or contrast with that sibling.
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?
No guidance on when to use this bulk variant versus stop_thread, nor any prerequisites or conditions for batching. The agent must infer the usage pattern entirely.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.