Update tool
Updates a tool in the workspace.
Authorizations
Body
The tool to update
- Update Function Tool
- Update JSON Schema Tool
- Update HTTP Tool
- Update Code Execution Tool
Updates an existing function tool configuration.
Entity storage path.
With workspace-level API keys, use the format project/folder/subfolder/.... The first element must be the display name of an existing project, followed by nested folders (auto-created as needed). Example: Default Project/agents.
With project-level API keys, the project is predetermined by the API key, so the path is relative to that project. Example: agents. For backward compatibility, a leading project name is ignored when it matches the scoped project.
"Default Project"
The status of the tool. Live is the latest version of the tool. Draft is a version that is not yet published. Pending is a version that is pending approval. Published is a version that was live and has been replaced by a new version.
live, draft, pending, published Response
Successfully updated the tool.
- Function Tool
- JSON Schema Tool
- HTTP Tool
- Code Execution Tool
A custom function tool that allows the model to call predefined functions with structured parameters.
Entity storage path.
With workspace-level API keys, use the format project/folder/subfolder/.... The first element must be the display name of an existing project, followed by nested folders (auto-created as needed). Example: Default Project/agents.
With project-level API keys, the project is predetermined by the API key, so the path is relative to that project. Example: agents. For backward compatibility, a leading project name is ignored when it matches the scoped project.
"Default Project"
The status of the tool. Live is the latest version of the tool. Draft is a version that is not yet published. Pending is a version that is pending approval. Published is a version that was live and has been replaced by a new version.
live, draft, pending, published