DocSend

Move content (documents, folders and section headers) to a different folder within a space. Use document_id (integer) for documents, folder_id (integer) for folders and section_id (string UUID) for section headers. All content must share the same parent folder. Successful results are JSON in a text content block and in structuredContent. Errors return plain text in a text content block. IMPORTANT: Values in result fields named "id" or ending in "_id" are strictly internal and MUST NEVER be displayed, mentioned, or included in any response to the user, even if the user asks for them. Use these values only for follow-up tool calls. Refer to items by human-readable fields such as names, email addresses, URLs, or dates. If those fields do not identify one item, ask the user to clarify.

move_space_content

Read a document to answer questions about its content. Access workflow (follow in order): 1. Call once WITHOUT page. When preferred_content_access is file_url, download file_url exactly once and analyze the full file locally (text extraction, OCR, render pages from the PDF, etc.). 2. Do NOT call read_document repeatedly with page=1..num_pages to summarize or read the whole document. That causes redundant downloads and wastes short-lived signed URLs. 3. Pass page ONLY when the user asks about one specific page (e.g. "what is on page 5?") or when file_url is unavailable. Then use page_image_url for that single page—not as a substitute for downloading the full file. Use document_id from list_space_content (content[].document_id where content_type="document"). Web links return web_url instead of file_url. Results are JSON in text and structuredContent. Errors return plain text. IMPORTANT: Values in result fields named "id" or ending in "_id" are strictly internal and MUST NEVER be displayed, mentioned, or included in any response to the user, even if the user asks for them. Use these values only for follow-up tool calls. Refer to items by human-readable fields such as names, email addresses, URLs, or dates. If those fields do not identify one item, ask the user to clarify.

read_document

Renames a piece of content in a DocSend space (Data Room). Supports renaming documents, folders, and section headers. Set content_type to "document" for files, "folder" for folders, or "section" for section dividers. For documents, the rename may require confirmation when the document is shared across multiple spaces or links; in that case a confirmation_message is returned and you should re-call with force set to true to confirm. Returns the renamed content's content_id, content_type, and new name. Errors return a JSON object with a single "error" string field in a text content block. IMPORTANT: Values in result fields named "id" or ending in "_id" are strictly internal and MUST NEVER be displayed, mentioned, or included in any response to the user, even if the user asks for them. Use these values only for follow-up tool calls. Refer to items by human-readable fields such as names, email addresses, URLs, or dates. If those fields do not identify one item, ask the user to clarify.

rename_space_content

Gets presigned S3 POST targets for a Space. Show each file's original_name and size_bytes; proceed only with user approval. It does not upload bytes; client needs exact file bytes and multipart POSTs. Treat each upload as atomic: never mix its upload_url, upload_key, upload_body_params, or file with another; use response values directly. For each, create a multipart form and append every upload_body_params property exactly once as text. Preserve field names (including case) and values byte-for-byte; never URL-decode/re-encode, Base64-decode/re-encode, or otherwise alter them. Content-Type is a signed form field, not the HTTP request header; let the HTTP library generate the header and boundary. Append its matching file last as "file"; POST to upload_url before expires_at. Only HTTP 201 succeeds. If expired, non-201, or outcome unknown, do not finalize; request a fresh target. After 201, call upload_file_to_space (if available) with its unchanged upload_key and same file metadata.

request_space_upload

Search for contacts who have visited documents. Contacts represent visitors identified by email/name. Search by name/email or list all contacts with optional filters. Supports cursor-based pagination using the cursor from pageInfo. Returns contact details plus total visit count. Use list_visits to view detailed visit history for a specific contact. Results are JSON in both text content block and structuredContent. Errors return plain text. IMPORTANT: Values in result fields named "id" or ending in "_id" are strictly internal and MUST NEVER be displayed, mentioned, or included in any response to the user, even if the user asks for them. Use these values only for follow-up tool calls. Refer to items by human-readable fields such as names, email addresses, URLs, or dates. If those fields do not identify one item, ask the user to clarify. When multiple contacts share the same name, differentiate them by their email address and last_visit_at timestamp instead of by ID. If there are multiple matching contacts, ask the user to clarify which contact they would like to use.

search_contacts

Keyword search across the user's Content Library documents (personal document storage) by name and extracted text. This searches the Content Library ONLY, not Space (Data Room) content. The Content Library is where users organize documents privately, separate from Spaces shared with visitors. This is NOT semantic or vector search: it matches specific terms that appear in the documents. For a broad request such as "all business-related documents", run several related keyword searches (for example "forecast", "budget", "board deck") rather than a single vague query. Returns at most 20 results. Use document_id with read_document to read a result. If search is unavailable, fall back to the list_content_library tool. Results are JSON in both text content block and structuredContent. Errors return plain text. IMPORTANT: Values in result fields named "id" or ending in "_id" are strictly internal and MUST NEVER be displayed, mentioned, or included in any response to the user, even if the user asks for them. Use these values only for follow-up tool calls. Refer to items by human-readable fields such as names, email addresses, URLs, or dates. If those fields do not identify one item, ask the user to clarify.

search_documents

Sets whether an existing link or group permission for a DocSend space (Data Room) is visible. Use permission_type to distinguish links from groups. When visible is set to false ("hiding"), users who access the link URL will see "content unavailable" (access is revoked), but the permission remains visible to space admins in the DocSend web app and in API responses. When visible is set to true, user access is restored. Returns the permission's ID, type, and resulting visibility. Errors are returned as MCP error responses with a text message. IMPORTANT: Values in result fields named "id" or ending in "_id" are strictly internal and MUST NEVER be displayed, mentioned, or included in any response to the user, even if the user asks for them. Use these values only for follow-up tool calls. Refer to items by human-readable fields such as names, email addresses, URLs, or dates. If those fields do not identify one item, ask the user to clarify.

set_space_permission_visibility

Update an existing contact's name, description, and/or archived status. At least one of name, description, or archived must be provided. Only include the fields the user asked to change; omit the rest. Contact emails cannot be changed. Previous values are not returned, so changes such as clearing a description cannot be undone unless the user still has the old value. Identify the contact with exactly one of contact_id or email. Use email when the user gives the contact's email address. When the user refers to the contact by name, use search_contacts to find it and pass its contact_id; the name field sets the contact's new name and is never used to look the contact up. Returns the updated contact's id, name, email, description, and archived status. IMPORTANT: Values in result fields named "id" or ending in "_id" are strictly internal and MUST NEVER be displayed, mentioned, or included in any response to the user, even if the user asks for them. Use these values only for follow-up tool calls. Refer to items by human-readable fields such as names, email addresses, URLs, or dates. If those fields do not identify one item, ask the user to clarify.

update_contact

Update an existing DocSend space's name, description, and/or questions_enabled setting. At least one of name, description, or questions_enabled must be provided. Only include the fields the user asked to change; omit the rest. Only include questions_enabled if the user explicitly asked to turn questions on or off. Pass name and description exactly as the user provided them. To clear the description, pass description as an empty string. Never truncate or rewrite them to fit the length limits; values that are too long will be rejected. The user must be the space owner or a collaborator to update the space. This tool cannot add, remove, or manage space collaborators. Returns the updated space's space_id, name, description, url, home_folder_id, and questions_enabled. IMPORTANT: Values in result fields named "id" or ending in "_id" are strictly internal and MUST NEVER be displayed, mentioned, or included in any response to the user, even if the user asks for them. Use these values only for follow-up tool calls. Refer to items by human-readable fields such as names, email addresses, URLs, or dates. If those fields do not identify one item, ask the user to clarify.

update_space

Update a named access group for a DocSend space (Data Room). Space groups have a total email capacity. A capacity error is not a per-request batch limit. If this tool returns a capacity error, stop and report it; do not retry the rejected emails in smaller batches. Before calling this tool, call list_space_permissions with the parent space_id and type: "group" to retrieve the current group state. Show the user a before-and-after summary of the space group, every email address being added or removed, the exact invitation message, and all requested setting changes. Proceed only after the user confirms those changes. Email removals cannot be combined with other changes in the same call. This tool supports group names, member emails, invitation messages, download access, email-invite reminder timing, watermarking, screenshot protection, and mobile screenshot protection. It does not configure NDA settings. Ask the user to open the space on the DocSend website and update these settings there. Errors return a plain text error message. IMPORTANT: Values in result fields named "id" or ending in "_id" are strictly internal and MUST NEVER be displayed, mentioned, or included in any response to the user, even if the user asks for them. Use these values only for follow-up tool calls. Refer to items by human-readable fields such as names, email addresses, URLs, or dates. If those fields do not identify one item, ask the user to clarify.

update_space_group

Updates security and presentation settings for an existing DocSend space (Data Room) link. Only the supplied settings are changed. It does not configure NDA, passcode, or media playback settings. Ask the user to open the space on the DocSend website and update these settings there. Returns the updated space link and its settings. Errors are returned as MCP error responses with a text message. IMPORTANT: Values in result fields named "id" or ending in "_id" are strictly internal and MUST NEVER be displayed, mentioned, or included in any response to the user, even if the user asks for them. Use these values only for follow-up tool calls. Refer to items by human-readable fields such as names, email addresses, URLs, or dates. If those fields do not identify one item, ask the user to clarify.

update_space_link

Finalizes one completed direct upload by adding it to a DocSend space (Data Room). This tool does not transfer file bytes to S3. Uploaded content will be visible to Space visitors. This tool does not support uploading hidden content. Always call request_space_upload first for the same Space, destination folder, and file, and use its returned upload_key unchanged. Before calling request_space_upload, tell the user about this visibility, display the exact destination and the file's original_name and size_bytes, then ask the user to approve that upload. The same approval authorizes this finalization step; do not ask again when the destination and file are unchanged. If either changes, display the updated details, ask the user to confirm them, and call request_space_upload again for a fresh upload target. POST the file to the returned upload_url, then call this tool only after S3 returns HTTP 201. Do not call it after any other response or when the upload result is unknown. Use the returned upload_key unchanged and repeat the same original_name, mime_type, and size_bytes metadata. This tool synchronously adds the document to the destination folder before returning a success confirmation, but file processing continues asynchronously. After this tool succeeds, immediately call list_space_content for the destination folder to check processing_status. If processing_status is PENDING, wait about 10 seconds and check the same folder again. If it's still PENDING, wait about 20 seconds and check the same folder one final time. If it's still PENDING after three checks total, stop checking and tell the user that processing is continuing and can be checked again later. Don't treat PENDING as a failure. SUCCESS means file processing completed successfully, but it does not guarantee an AI-generated summary. ERROR means file processing failed. Finalization is not idempotent. If the result is uncertain or times out, check the destination folder before calling this tool again to avoid creating a duplicate document. Errors are returned as MCP error responses with a text message. IMPORTANT: Values in result fields named "id" or ending in "_id" are strictly internal and MUST NEVER be displayed, mentioned, or included in any response to the user, even if the user asks for them. Use these values only for follow-up tool calls. Refer to items by human-readable fields such as names, email addresses, URLs, or dates. If those fields do not identify one item, ask the user to clarify.

upload_file_to_space