Dropbox Dash

Execute a read-only search action on a source using its native API. This tool only reads data — it does not create, update, or delete anything. It requires no write permissions. WORKFLOW: dash_get_sources → dash_list_search_actions → dash_invoke_search_action (this tool) PARAMETERS: - connection_id (string, required): Connection ID from dash_get_sources (must have supports_actions=true) - tool_name (string, required): Action name from dash_list_search_actions - tool_params (object, required): Parameters matching the action's inputSchema RETURNS: Action-specific result object. Structure varies by action; see outputSchema from dash_list_search_actions.

dash_invoke_search_action

Fetch a document’s metadata and extracted text by document ID. Use this after the search tool has returned a document ID and the assistant needs to read that specific document’s contents or inspect its metadata. This tool is read-only and does not modify any data. Returns metadata and extracted text content. If the response has has_more=true, use dash_read_markdown_content to fetch remaining content. For visual page renderings (PDFs, slides), use dash_read_visual_page instead. For raw binary files (images, video, audio), use dash_read_binary_content instead. Do NOT use this tool to discover documents by keyword or topic; use the search tool first. Do NOT invent document IDs. WORKFLOW: search -> fetch (this tool) -> dash_read_markdown_content (if has_more) RETURNS: - id: Document ID - title: Document title - text: Extracted document text. May be truncated for large documents. - url: Direct link to the document. - metadata: Document metadata, including connector_type, doc_type, mime_type, and updated_at. Use mime_type to determine if the document requires visual or binary content tools. - has_more (boolean): True if additional document text is available beyond this response.

fetch

Get the current user's identity information. This tool is read-only and does not modify any data. WHEN TO CALL: Whenever the user's request contains personal references like "me", "my", "mine", "own", "assigned to me", or "I created". Call this BEFORE dash_search to get the user's email for use in filters like relation.assigned_to or relation.creator. PARAMETERS: None required. RETURNS: - display_name: User's full name (e.g., "John Smith") - email: User's email address (e.g., "[email protected]") EXAMPLE: When user asks "find my documents", first call dash_whoami to get their email, then search with that email as a filter or in the query.

dash_whoami

Get the required filter schema for a specific source type. This tool is read-only and does not modify any data. This is the ONLY source of truth for valid filter field names, values, and query patterns. You MUST call this before using filters in dash_search — do not guess or invent field names. WORKFLOW: dash_get_sources → dash_get_examples (this tool) → dash_search PARAMETERS: - connector_type (string, required): Must be obtained from dash_get_sources. Do not guess or hardcode connector types — they use inconsistent casing and vary per user. RETURNS: Unstructured text describing: - Available label_filters with field names (use these EXACTLY in dash_search filters) - Valid values for each filter field - Example queries and filter combinations - Best practices for searching this source EXAMPLE: First call dash_get_sources to get connector_type values, then call dash_get_examples with a connector_type from that response to learn its filters before calling dash_search.

dash_get_examples

List all connected sources available to the user. This tool is read-only and does not modify any data. Returns source types, display names, and connection IDs needed by other tools. Call this FIRST before using connector_type in any other tool — available connectors vary per user and types use inconsistent casing that cannot be guessed. If the user's query references "me", "my", "mine", or "own", also call dash_whoami to resolve the user's identity before searching. RETURNS: Array of connections, each with: - connector_type: Source type identifier (use this value exactly in other tools) - name: Display name - description: Source capabilities - icon_src: URL to the source's icon (SVG format) - connection_id: Encrypted identifier for this specific connection - supports_actions: Whether this connection supports search actions - connection_status: Auth status — "CONNECTED" (healthy), "REAUTH" (needs re-authentication, data may be stale or missing), or "EXPIRED" (inactive) - last_successful_sync_time: RFC3339 timestamp of when data was last fully synced. Empty means initial sync never completed — data may be partial - sync_state: Sync lifecycle — "synced" (data up to date), "syncing" (initial sync in progress), "not_started" (no sync initiated), or "error" (sync failed) - upgrade_available: Whether the connection needs re-authentication to get newer capabilities (true when a newer connector version exists or granted scopes are incomplete) WORKFLOWS starting from this tool: - Filtered search: dash_get_sources → dash_get_examples → dash_search - Search actions (only for connections with supports_actions=true): dash_get_sources → dash_list_search_actions → dash_invoke_search_action

dash_get_sources

List available search actions for a source. This tool is read-only and does not modify any data. Discovers source-specific read-only actions that query data from a source. These actions use the source's native API, unlike dash_search which provides a unified search across all sources. Both this tool and the actions it lists are strictly read-only. WORKFLOW: dash_get_sources → dash_list_search_actions (this tool) PARAMETERS: - connection_id (string, required): Connection ID from dash_get_sources (must have supports_actions=true) RETURNS: Array of search actions with name, description, inputSchema, and optional outputSchema. All actions are read-only.

dash_list_search_actions

Read raw binary content (images, video, audio files) from a Dash document as base64-encoded data. This tool is read-only and does not modify any data. Use for non-text files where you need the actual binary data. For text documents, use dash_read_markdown_content instead. For visual page renderings, use dash_read_visual_page instead. WORKFLOW: dash_search → dash_read_binary_content (this tool) IMPORTANT: Exactly one of uuid or uri must be set. Use offset and limit for range queries on large files. Pass consistency_token from the response to subsequent calls to detect content changes across chunked reads.

dash_read_binary_content

Get document metadata and optionally extract text content for a specific Dash document. This tool is read-only and does not modify any data. Returns metadata (title, URL, type, timestamps) and optionally extracted text content via include_body. If the body response has has_more=true, use dash_read_markdown_content with the returned next_offset to fetch remaining content. For visual page renderings (PDFs, slides), use dash_read_visual_page. For raw binary files (images, video, audio), use dash_read_binary_content. WORKFLOW: dash_search → dash_read_document (this tool) → dash_read_markdown_content (if has_more) IMPORTANT: Exactly one of uuid or uri must be set — not both.

dash_read_document

Retrieve stored embeddings for one or more Dash entities identified by UUID, URI, or Dropbox file path. This tool is read-only and does not generate new embeddings. Each returned vector includes its stored model identity and dimensions, plus its kind, modality, source field, storage facet and revision, and storage update timestamp. Only compare or cluster vectors whose non-empty model identities and dimensions match. Use the optional kinds parameter to restrict results to one or more embedding kinds: title, body, image, image_analysis, or ocr_text. Omit kinds to return every supported kind. Targets that cannot be resolved or accessed, or have no matching stored embeddings, are returned in unavailable_targets without failing the rest of the request. WORKFLOW: dash_search → dash_read_embeddings (this tool) IMPORTANT: At most 100 targets may currently be requested per call. The caller must have Dash content-read access to returned entities.

dash_read_embeddings

Read document content as markdown, with chunked transfer support for large files. This tool is read-only and does not modify any data. Typically used as a follow-up to dash_read_document with include_body=true when the body response has has_more=true — use next_offset from that response to continue reading. Can also be called directly to read content from scratch. For visual page renderings (PDFs, slides), use dash_read_visual_page instead. For raw binary files (images, video, audio), use dash_read_binary_content instead. WORKFLOW: dash_search → dash_read_document (include_body=true) → dash_read_markdown_content (this tool, if has_more) IMPORTANT: Exactly one of uuid or uri must be set. Use offset and limit for chunked reads. Pass consistency_token from the response to subsequent calls to detect content changes across paginated reads. If has_more is true in the response body, use next_offset to fetch the next chunk.

dash_read_markdown_content