Remove a previously registered preload script by its identifier. This unregisters the script from the browser.
Remove a previously registered preload script by its identifier.
| Name | Required | Description | Default |
|---|---|---|---|
| identifier | Yes | Script identifier returned by browser_add_preload_script |
Changes observed during successful MCP inspections.
v0.8.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It does not say what happens if the identifier is unknown, whether removal takes effect immediately or on next navigation, whether it is reversible, or what is returned — all material for a mutation tool.
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?
One short sentence, front-loaded with verb and resource, with zero filler. Every word earns its place.
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?
The tool is simple (one required string, no nested objects, no output schema), so little is strictly needed, but with no annotations at all the description should at minimum state the effect of an invalid identifier and whether removal is immediate. Those gaps keep it at minimum-viable rather than complete.
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 coverage is 100% and the single parameter is described in the schema itself as "Script identifier returned by browser_add_preload_script," which the description merely restates. No additional syntax, format, or edge-case meaning is added, so the baseline of 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 (remove) plus resource (preload script) and constrains it to a previously registered script identified by identifier. It is unambiguous among the large sibling set, which contains only one counterpart (browser_add_preload_script).
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 phrase "previously registered" implies the prerequisite that a script must first exist, but there is no explicit when-to-use guidance, no mention of when removal is unnecessary, and no reference to the sibling add tool. Usage is inferable but not stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.