Read tools

Search, browse, and look up iManage Work content

fetch

  • Description: Downloads and returns the text content of the document for the specified ID.

  • Sample prompt: Fetch ACTIVE_US!12345.7
    (Pasted this ID in the chat to know whether it's a document or workspace).

get_container_children

  • Description: Gets the children of a container from given container_id. Returns a maximum of 500 folders, documents, and tabs in a single call. Call this tool to iteratively get all children of a container. Valid container types are workspace, tab, and folder.

  • Sample prompt: Fetch items for workspace ACTIVE_US!12345.7.

get_recent_documents

  • Description: Gets recently accessed documents by the current user. The documents are sorted by the most recently accessed first. Document properties can be used to filter and truncate the results.

  • Sample prompt: Get recent documents from iManage Work.

get_recent_workspaces

  • Description: Gets recently accessed workspaces or matters by the current user.

  • Sample prompt: Get recent workspaces from iManage Work.

list_actions

  • Description: Lists recent document moves performed using the move_document tool. Other MCP tool actions (such as creating a workspace) aren't tracked here, and neither are document moves performed directly in iManage Work rather than through the move_document tool. Shows action details, status, and whether each action can be undone.

  • Sample prompts:

    • What document moves have I made using the move document tool recently, and which ones can I undo?

    • Show me my recent document moves performed through the move document tool in iManage Work.

  • Description: Performs intent-aware natural-language search across iManage Work, covering document names, descriptions, comments, full-text content, and workspace names/descriptions. Use this tool whenever the user is looking for existing documents, examples, templates, prior matters, emails, or a workspace related to a specific issue, person, or matter. Intent Interpretation: Before forming the query, identify what the user is trying to find—such as a specific document, a type of template, similar past work, matter-related material, or all documents related to an event or concept. Query Construction: Rewrite the user request into a single, concise, meaning-rich search phrase. Extract key elements such as: • document type (e.g., NDA, contract, memo, settlement) • legal or business concepts (e.g., garden leave, termination, indemnity, breach) • names of clients, counterparties, employees, or entities • matter numbers or workspace IDs • jurisdictions or regions • relevant time references. Include synonyms or related terms only when they clearly reinforce the user's intent, not as broad expansions. Search Strategy: Run one well-constructed search per user query. Do not perform multiple incremental searches unless the user explicitly asks to refine or explore further. Choosing Search Targets: • Favor documents when the user wants examples, templates, drafts, contracts, emails, or prior material. • Favor workspaces when the user references a matter ID, case folder, or wants to see all content tied to a matter. The tool returns the most relevant documents or workspaces based on the interpreted intent and the optimized search phrase.

  • Sample prompt: Search for Data points extraction from iManage Work.

search_documents

  • Description: Performs intent-aware search for documents within iManage Work by document name. Use this tool when the user is trying to locate a specific document whose name or naming pattern is known, implied, or reasonably inferable. Intent Interpretation: Determine whether the user is looking for a particular title, a specific version ("final", "signed", "draft"), a named file they previously encountered, or a document that follows known naming conventions. Query Construction: Create a precise document-name-focused search phrase that captures the naming intent. Include: • keywords from expected title • client/employee/counterparty names • prefixes/suffixes ("Final", "Draft", "Signed") • matter/project naming patterns • dates or versions explicitly mentioned. This tool strictly performs name-based lookup—do not expand into topic or content-level concepts. Search Strategy (with fallback): Perform one primary search using the best inferred name. If that search returns no results and the user strongly implies the document exists, you may execute one fallback search using a simpler or slightly broader name pattern (e.g., removing version tags, date details, or unnecessary qualifiers). Do not perform more than one fallback attempt. When to Prefer This Tool: • The user refers to a known document title. • The user mentions a version ("final", "signed version", "Q1 draft"). • The user indicates a specific file they expect to retrieve. Returns the closest matching documents based on name relevance.

  • Sample prompt: Search for Lease due diligence report.pdf.

search_folders

  • Description: Searches for folders in iManage Work by name within a specific workspace or parent folder. Supports wildcard matching in the name (for example, report).

  • Sample prompts:

    • Search for a folder named "Draft Agreements" in the Vendor Agreement Review workspace.

    • Search for folders with names containing "report" in the ACME!123 workspace.

search_workspaces

  • Description: Searches for workspaces based on the provided criteria.

  • Sample prompt: Who owns the <Workspace name> workspace? Also give me their user info.

Download documents and inspect document content, versions, and properties

download_document

  • Description: Downloads the text content of a document based on its ID. Supports retrieving the latest version.

  • Sample prompt: Download document with the WORKDB1!1612117.1 ID from iManage Work.

NOTE: Provide the name of the iManage Work item (workspace, folder, document name, and so on) to your MCP-enabled client and ask it to fetch the ID. Then, you can use the ID in this or other prompts, as needed.

get_document_profile

  • Description: Gets the document properties associated with a specific document ID. Document properties includes the client and workspace information.

  • Sample prompt: Get document profile for WORKDB1!1612117.1

get_document_versions

  • Description: Gets the complete version history of a document, including all version metadata such as version numbers, authors, modification dates, file sizes, and comments. Returns up to 1000 versions. Each version includes the full document profile.

  • Sample prompt: Get document version history of <Document name>.

get_rows_from_csv_document

  • Description: Gets all the rows from a CSV document.

  • Sample prompt: Get all rows from the CSV document WORKDB1!1612117.1.

View workspace profile and templates

get_workspace_profile

  • Description: Gets the profile for the workspace from given ID from input.

  • Sample prompt: Get workspace profile for JAPAN_1!62.

get_workspace_templates

  • Description: Gets list of workspace templates available in a library. Workspace templates are predefined folder structures used to create consistent, organized workspaces for legal matters within a document management system. They help ensure compliance and standardization across client and matter files.

  • Sample prompt: Get the workspace template with the title <Template name> from the workdb1 library.

Access user details and available libraries

get_libraries

  • Description: Gets all the libraries for the current user.

  • Sample prompt: Get all libraries.

get_user_information

  • Description: Gets information about users in the iManage Work system. A user in iManage Work may be associated with documents as an author or have access to documents as a reviewer or collaborator. They may also be owners of a workspace or have tasks assigned to them. Returns information about the current user when the query is an empty string.

  • Sample prompt: Get user information.

Write tools

Create workspaces, folders, and document relationships

create_document_relation

  • Description: Creates a bidirectional relationship between two documents, linking them so each shows up as related to the other. Both documents must be in the same library, and a document cannot be related to itself. If the relationship already exists, the operation still reports success rather than raising an error.

  • Sample prompts:

    • Relate the "Purchase Agreement" document to the "Closing Memo" document in the Smith v. Jones workspace.

    • Create a relation between the "Vendor Contract" document and the "Amendment 1" document in the Vendor Agreement Review workspace.

create_folder

  • Description: Creates a new folder under a workspace, a tab, or another folder. You can set the folder's name, owner, description, default security ('Inherit', 'Private', 'View', or 'Public'), class/subclass, and custom fields. By default, the new folder inherits custom property values from its parent workspace, though this can be turned off.

  • Sample prompt:

    • In the <Project Name> workspace, create a "Third-Party Consents" folder.

    • Create a subfolder called "Draft Agreements" under the Contracts folder in the Vendor Agreement Review workspace, with security set to "private".

    • Create the "Discovery Documents" folder under the Smith v. Jones workspace, owned by jsmith.

create_workspace

  • Description: Creates a new workspace based on a template. A template is an existing workspace whose folder structure is copied into the new workspace, and any restrictions configured on the template are automatically enforced on the new workspace. The template's ID must be looked up first (for example, using the "get workspace templates" tool) before creating the workspace. You can choose to create all folders from the template or only the required ones, and optionally set a workspace name, description, owner, default security level, and other custom fields.

  • Sample prompts:

    • Spin up a new workspace "<Client> – <Matter>" using our "M&A" template and make it private.

    • Create the "Johnson Estate" workspace in the ACTIVE_US library using the "Estate Planning" template, set the owner to jsmith, and make the default security "private".

    • Create a workspace called "Acme Merger 2026" in the ACTIVE_US library from the "M&A Deal" template, creating only the required folders.

Update workspace and document details

update_document_profile

  • Description: Updates the profile fields of a document, identified by its document ID. You can update fields such as the name, author, class, subclass, comment, custom fields, and other profile properties, by supplying just the fields you want to change.

  • Sample prompts:

    • Update security for WORKDB1!1612117.1 as view-only and add "Final executed version – do not edit." to comments.

    • Add a comment to the "Closing Memo" document in the Acme Merger 2026 workspace: "Final version approved by legal."

    • Update the class of the "Vendor Contract" document in the Vendor Agreement Review workspace to "Contracts" and the subclass to "NDA."

update_workspace

  • Description: Updates the profile of an existing workspace, identified by its workspace ID. You can update fields such as the name, owner, description, default security, subclass, and various custom fields. Only the fields you specify are changed. Any fields left out are unaffected, and if a value you provide matches what's already set, no update is made for that field.

  • Sample prompts:

    • Update the description of <Workspace name> workspace to "Acme – 2025 refinancing" and set custom21 to the signing date.

    • Change the owner of the Johnson Estate workspace to "jsmith."

    • Update the Vendor Agreement Review workspace: Set the custom1 field to "High Priority" and clear the custom2 field.

Move and upload documents

move_document

  • Description: Moves a document from one iManage Work folder to another. The source and destination folders must belong to the same library: Moving a document across libraries isn't supported. By default, after the move, profile and security of the document are updated to match the destination folder; both of these can be turned off if you want the document to keep its original profile and/or security instead. You can also add a comment describing the move, which appears in the document's activity timeline.

  • Sample prompts:

    • Move <DocID> from Drafts to Executed Agreements and update profile/security to match the destination. Add the comment "Signed"

    • Move the "Purchase Agreement" document from the Draft Contracts folder to the Executed Contracts folder in the Smith v. Jones workspace.

    • Move the "NDA Draft" document to the Executed Contracts folder in the Johnson Estate workspace, but keep its current profile and security instead of inheriting from the destination folder.

    • Move the "Closing Memo" document from the Correspondence folder to the Final Documents folder in the Acme Merger 2026 workspace, and add the "Relocated to closing docs per client request." comment.

upload_document

  • Description: Creates and uploads a new document into a specified folder. You can generate the document as a PDF (the default) or as a Microsoft Word (DOCX) file: Just describe the content you want, and it's written out and uploaded in the chosen format. Content is limited to 128KB. If you don't specify a document name, one will be generated based on the conversation.

  • Sample prompts:

    • Create a PDF summarizing the key settlement terms for the Smith v. Jones case, and upload it to the Correspondence folder in the Smith vs. Jones workspace.

    • Write a one-page NDA template as a Microsoft Word document and upload it to the Draft Agreements folder in the Vendor Agreement Review workspace; name it "NDA Template".