list_node_types. Requires Viewer or higher in the applicable workspace and a connected OAuth session.
Returns spec_version and available node types with summary, category, and display name. Inspect get_node_type for configuration before authoring a node. Keep track of the specification version when generating definitions.
Arguments
Send an empty arguments object:{}.
Example arguments
Replace sample resource IDs with IDs returned in your selected workspace.Result and errors
The schema below describes MCPstructuredContent, including the result wrapper where present. Your client may also display a text representation. Read success flags and structured errors before continuing; transport success alone does not prove the operation succeeded. Authentication, missing membership, and insufficient role can fail before a tool result is produced. See troubleshooting.
Effect: Reads data. Retry: Declared idempotent. Discovery annotations describe behavior; they do not grant permission or replace confirmation for consequential actions.
Input schema
Input schema
Result schema
Result schema