MCP Tool
nova.bookmarks_folder_create
For user artifacts, notices, and small work handoffs, an agent uses this public tool to carry out the bounded step "Bookmark-Folder Create/Rename". It separates target confirmation, intended state change, and verification after execution.
Canonical reference for a public MCP tool name.
- Type
- MCP tool
- Family
- Favorites & Clipboard
- Effect
- changes state
- Status
- Explained
- Path
- 20.9
Purpose
What this entry explains
What it does
nova.bookmarks_folder_create
An agent uses this tool to carry out the bounded step "Bookmark-Folder Create/Rename". It belongs to user artifacts, notices, and small work handoffs; agents should combine it with current discovery, target awareness, and the visible result.
Use when
- Use this entry when an agent needs to carry out the bounded step "Bookmark-Folder Create/Rename" for user artifacts, notices, and small work handoffs.
- Use it to understand the public tool name, its expected boundary, and the response signals to check.
- Use it before chaining follow-up tools so the next step is based on current evidence.
Reference Use
How agents should cite and apply this area
Examples are maintained at family level and use only public tool names or reference paths already present in the catalog.
Family example
A task in user artifacts, notices, and small work handoffs can trigger powerful execution and therefore needs target, approval, and result check before the step.
The agent starts with nova.favorites_add, reads the current response or reference, and only then chooses the concrete next tool.
Current discovery, target, user control, warning signals, and result check come before execution.Contract
Inputs and important response fields
This page is a public reference. Agents and integrators should still read current MCP tool discovery before execution, because schemas can be gated by settings or version.
Inputs
name
Name for the target object. Check uniqueness before creating or changing it.
parentId
Reference key for the current target, object, or session. Read it from the current response instead of guessing.
id
Reference key for the current target, object, or session. Read it from the current response instead of guessing.
Response fields
No fixed public response field is derived from the catalog source for this path. Use current tool discovery and the actual response before chaining the next step.
Safety
Boundary before execution
Can change browser, page, or workflow state. The target and expected result must be clear before execution.
Confirm the current target first, perform only the intended bounded action, and verify the resulting page or workflow state afterwards.
For humans, this entry names the browser or workflow state in user artifacts, notices, and small work handoffs that may change, so the action can be reviewed before and after execution.
High-Impact Review
Execution boundary and recheck hints
Review category: Clipboard/site data/cookies/storage
Cookies, storage, cache, and clipboard stay limited to origin, purpose, and current user control.
False assumption: site data is only technical configuration and not user-related.
Origin, data kind, planned change, and expected effect must remain visible.
Do not guess, log, or reuse cookies, storage values, or clipboard contents across domains.
Stop if origin, value, delete effect, or target page does not clearly match the current task.
Safety Axes
How this path can affect work
Axes are stable catalog signals for humans, agents, and LLM discovery. One path can carry several axes.
persistent_change
Saves, deletes, remembers, schedules, or changes data that may outlive the immediate page state.
Execute only with clear scope and keep the saved, deleted, or scheduled effect reviewable.sensitive_data
Touches cookies, storage, clipboard, credentials, tokens, user content, identity, or private data.
Use only with bounded purpose and visible user control; do not guess, log, or forward sensitive values.user_confirmation
Requires visible confirmation, target review, approval, or deliberate user control.
Do not proceed until the required confirmation is visible or unambiguous in the current context.