> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tryprofound.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Profound Docs
> Understand the Profound Docs tools available through Profound MCP
Profound MCP gives AI assistants tools to find, read, write, and manage documents in Profound Docs, the collaborative documents in the Profound platform, such as memos and briefs. To connect your MCP client to the hosted server, refer to the [Connection guides](/mcp/common-mcp-clients).
Documents in Profound Docs are not Knowledge Base documents. To add content that AI assistants and Agents search and retrieve, use the `add_knowledge_base_document` tool instead. Refer to [Knowledge Base](/mcp/capabilities/knowledge-base-capabilities).
## How the tools work together
Ask whether a document exists or which ones changed recently. The assistant searches document names with `list_docs` and links you to each result.
Ask for a summary or the full text. The assistant reads the document with `get_doc`, skimming the opening by default and loading the whole body when the task needs it.
Ask for a new document and the assistant drafts and saves it with `create_doc`. Ask for a change to an existing one and it rewrites the document with `replace_doc_content`.
Ask to rename a document or change who sees it (`update_doc`), or to delete one the assistant created earlier (`delete_doc`).
## Behavior and safety
Write tools default to preview mode: the assistant receives a plan of the change first, and nothing changes until it applies that plan. The exception is `delete_doc`, which has no preview and deletes on the first call.
### Behaviors
| Behavior | What it means |
| ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Preview before apply | `create_doc`, `replace_doc_content`, and `update_doc` return a plan first, and report `applied: true` only once a change is applied |
| Whole-document writes | `replace_doc_content` overwrites the entire body and clears comments and tabs on every call, including full-body and partial rewrites |
| Last write wins | The replace tool doesn't check versions. When two writers replace the same document, the later write overwrites the earlier one, with no rollback |
| Rename and reshare restrictions | `update_doc` works only for documents created through MCP or ones you created yourself in the Profound platform. Only a document's creator can change its visibility |
| Delete restrictions | `delete_doc` works only for documents created through MCP. Asking to delete one you made in the Profound platform returns `deleted: false` |
| Live data | Tools read from the Profound API, so results reflect your current access and data |
### MCP hints
The following MCP hints are set on the write tools.
| Tool | Hints | What it means |
| --------------------- | ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `create_doc` | `destructiveHint: false`, `idempotentHint: true` | Creating twice with the same `name` returns the existing document instead of a second copy, and creating never overwrites an existing document |
| `replace_doc_content` | `destructiveHint: true`, `idempotentHint: true` | The call overwrites the entire body and clears comments and tabs |
| `update_doc` | `destructiveHint: true`, `idempotentHint: true` | A rename permanently stops the title from following the first heading, and re-sending `visibility: organization` downgrades existing edit access to view-only |
| `delete_doc` | `destructiveHint: true`, `idempotentHint: true` | A deleted document can't be restored through any API, and a repeat call reports `deleted: false` |
Every write tool also sets `openWorldHint: true`, which tells your MCP client that the writes land in the live, shared environment, so the client may ask you to confirm before running them.
## Profound Docs tools
| Tool | Usage |
| --------------------- | ------------------------------------------------------------ |
| `list_docs` | Find documents by name and read their details |
| `get_doc` | Read one document, as a preview or in full |
| `create_doc` | Create a new document from drafted content |
| `replace_doc_content` | Replace a document's entire body, clearing comments and tabs |
| `update_doc` | Rename a document, change who can see it, or both |
| `delete_doc` | Delete a document this integration created |
Finds documents and their details, such as the name, owner, visibility, and link (`url`). Results are ordered by most recently modified first and never include the document body.
**Example prompts**:
* "Do we already have a doc about our AEO strategy?"
* "Which Profound docs changed most recently?"
**Inputs**
| Input | Required | Default | Description |
| ----------------- | -------- | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `q` | No | `null` | Approximate match on the document name. It doesn't search the document body |
| `sort` | No | `null` | `recency` is the only accepted value, and it matches the default ordering. Any other value returns an error |
| `organization_id` | No | `null` | Organization whose documents to list. Defaults to the session's organization (if resolved). Required when the account has access to more than one organization |
| `limit` | No | `20` | Documents returned per page of results, 1–50. Values outside the range return an error |
| `cursor` | No | `null` | The `next_cursor` from a previous call, used to fetch the next page. It expires one hour after it's issued |
**Limitations**:
* The tool doesn't filter by document author or owner. To find one person's documents, the assistant lists all documents and reads each row's owner, which can take a while.
* The tool doesn't return a total document count.
Reads one document. The default preview returns only the opening of the body. When the task needs the full text or the discussion on it, the assistant loads the complete body or the comments.
**Example prompts**:
* "Summarize the AEO strategy memo."
* "Read the Q3 retro in full, including the comments people left on it."
**Inputs**
| Input | Required | Default | Description |
| ------------------ | -------- | ------- | --------------------------------------------------------------------------------------- |
| `doc_id` | Yes | - | The document's ID, from `list_docs` or a document URL |
| `organization_id` | Yes | - | The organization that owns the document |
| `preview` | No | `true` | `true` returns the opening of the body; `false` returns the complete body |
| `include_comments` | No | `false` | `true` also returns comments, each with the comment text and the passage it was left on |
Creates a new document from content the assistant has drafted. The tool takes the complete body in one call.
**Example prompts**:
* "Write a Q3 AEO retro based on this quarter's visibility data and save it as a Profound doc."
* "Draft a competitor brief and store it in Profound so I can share it later."
**Inputs**
| Input | Required | Default | Description |
| ------------------ | -------- | ------- | ----------------------------------------------------------------------------------- |
| `name` | Yes | - | Title for the document, at most 256 bytes. Also its identity within an organization |
| `content_markdown` | Yes | - | The complete body as Markdown, at most 1,000,000 bytes |
| `organization_id` | No | `null` | Organization to create the document in. Defaults to the session's organization |
| `preview` | No | `true` | When `true`, return the plan without creating the document; when `false`, create it |
**Notes**:
* Document titles are unique within an organization: creating a document with a title that already exists returns the existing document and discards the new body.
* New documents are visible only to their creator.
* When the call fails between creating the document and storing its body, the document exists but is empty, and the response reports `content_written: false`. A retry returns the same empty document instead of filling it.
Use with caution: this tool replaces the entire document body, clears all tabs except the main tab, and clears all comments.
Replaces a document's content with new text. Any change to an existing document, from ticking a box to rewriting a section, goes through this tool.
**Example prompts**:
* "Add a section on shopping prompts to the AEO strategy memo."
* "Fix the typos in the Q3 retro."
**Inputs**
| Input | Required | Default | Description |
| ----------------- | -------- | ------- | -------------------------------------------------------------------------------------------- |
| `doc_id` | Yes | - | The document to replace, from `list_docs` or its URL |
| `content` | Yes | - | The complete new body as Markdown. An empty value clears the document |
| `organization_id` | No | `null` | Defaults to the session's organization |
| `skip_title_sync` | No | `false` | `true` keeps the current title. By default the title follows the new content's first heading |
| `preview` | No | `true` | When `true`, report what the overwrite would change; when `false`, write |
**Notes**:
* When the document content is replaced, the title updates to match the new content's first heading, unless `skip_title_sync` is `true`.
Renames a document, changes who can see it, or both in one call.
**Example prompts**:
* "Rename the strategy memo to 'AEO strategy H2'."
* "Make the Q3 retro visible to the whole organization."
**Inputs**
| Input | Required | Default | Description |
| ----------------- | -------- | ------- | -------------------------------------------------------------------------------------- |
| `doc_id` | Yes | - | The document to rename or reshare |
| `name` | No | `null` | New title, at most 256 bytes. Omit when the title isn't changing |
| `visibility` | No | `null` | `invited_only` or `organization`, which is view-only. Omit when sharing isn't changing |
| `organization_id` | No | `null` | Defaults to the session's organization |
| `preview` | No | `true` | When `true`, return the plan without changing anything; when `false`, apply |
**Notes**:
* At least one of `name` or `visibility` is required. A call with neither returns an error.
* A document rename doesn't change the document's first heading, and permanently stops the title from following it. For example, if you rename "AEO strategy" to "AEO strategy H2", the first heading of the document still says "AEO strategy".
* View-only is the sole access level that `update_doc` can grant to everyone at an organization. If everyone at an organization already has edit access, setting `visibility` to `organization` through MCP downgrades that access to view-only.
* The tool works only for documents created through MCP or ones you created yourself in the Profound platform. A document shared with you, even with edit access, can't be renamed or reshared, and only its creator can change its visibility.
Deletes a document the assistant created through an MCP connection earlier, such as a draft that turned out wrong or a duplicate. This is the one write tool with no preview mode.
**Example prompts**:
* "Delete the draft you created earlier, we're keeping the final version."
* "That brief turned out to be a duplicate, remove it."
**Inputs**
| Input | Required | Default | Description |
| ----------------- | -------- | ------- | --------------------------------------------------- |
| `doc_id` | Yes | - | The document to delete, from `list_docs` or its URL |
| `organization_id` | No | `null` | Defaults to the session's organization |
**Notes**:
* Deletion works only for documents created through MCP, and only by their creator.
* Deletions are final: you can't undo them.
## Resources
| Resource URI | Use it for |
| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `file:///profound/docs-guide` | The authoring playbook: how a document differs from a Knowledge Base document, when to create and when to replace, how to safely overwrite a whole document, and who can see a new document |
| `file:///profound/glossary/doc` | The definition of a Profound Doc |