Carta CRM

find company by domain

Return Contact by id, with deals and notes (globalNotes property) this user related to

return user interactions by emails of target user. if email or emails doesn't exist in user request you can use search_contacts tool and use email_detail, email_detail_second, email_detail_fourth, email_detail_third properties to get target contact emails

response schema { emailRelationsCount: number (represent count of emails with this contact) eventRelationsCount: number (represent count of events such as calls, and meetings with this contact) totalRelationsCount: number (just sum of emailRelationsCount and eventRelationsCount)

relations: [{ title: string (name of event or email) toEmails: [{ email: string (email of contact) name: string; (name of contact) domain: string; (domain that represent company of contact) }] (toEmails is array of objects with info who was in event, or email receivers) fromEmails: string (email of creator event or email) type: 'EVENT' | 'EMAIL'; (if EVENT it's call or meeting, if EMAIL it's email) startDate: string (date of email or meeting) }] (array of object represent interaction with this user)

futureInteractions: array of the same object as in relations, but represent future interaction }

Return deal by deal Id, return one deal with more details, with all notes, people related to deal. Use this tool to achieve all needed info about deal. CRITICAL INSTRUCTION: Link References in Responses When generating responses that reference external resources, documents, or objects, you MUST always include the link reference directly in the response text itself, using the URL property from the response object. Requirements: 1. Extract the URL from the response object's url property 2. Embed the link naturally within the response text 3. Use this markdown format [Link Text](link) 4. Place links contextually where they're most relevant 5. Never assume the user can access the URL elsewhere - include it inline 6. Always put reference link if mention content from note, deal

search companies by search string. Return schema { realReturnCount: real count of returned items regardless of specified limit; count: number (all count of items in search); remainingCount: count of items that not fetched; data: array of companies sliced by pagination; } tool can return less items than was specified in limit in such case for next request use offset = prevOffset + realReturnCount. To understand that you can fetch additional items use remainingCount filed in response if it's not 0 you can continue fetch CRITICAL INSTRUCTION: Link References in Responses When generating responses that reference external resources, documents, or objects, you MUST always include the link reference directly in the response text itself, using the URL property from the response object. Requirements: 1. Extract the URL from the response object's url property 2. Embed the link naturally within the response text 3. Use this markdown format [Link Text](link) 4. Place links contextually where they're most relevant 5. Never assume the user can access the URL elsewhere - include it inline 6. Always put reference link if mention content from note, deal

Return Contacts by search string and listId. Contacts in system ordered by lists and folders, it's hierarchy of lists and folders, { listId: value for search listName: value that user can ask in request type: list; } { folderName: value that user can ask in request type: folder; inside: lists and folders inside this folder } CRITICAL RULES for Contact Search by lists and folders: 1. When user mentions a folder name:

• Always search ALL lists contained within that folder
• if folder contains another folder check list inside this folder too
• Exception: Only search specific lists if the user explicitly specifies them

2. When there is a GOOD/STRONG match for a list or folder name. A "good match" includes: exact matches, clear synonyms, or obvious references to the list/folder name:

• DO NOT use the query parameter for search by string in GOOD/STRONG match case.
• ONLY use the list_id parameter with the matching list/folder's ID

This ensures precise targeting and avoids irrelevant results [{"listId":"list-d65c-4088-9207-525b4c01e329-ebc-d98a04a6f-3675a-2875582","listName":"Contacts","type":"list"},{"listId":"all-contacts","listName":"All Contacts","type":"list"}] CRITICAL INSTRUCTION: Link References in Responses When generating responses that reference external resources, documents, or objects, you MUST always include the link reference directly in the response text itself, using the URL property from the response object. Requirements: 1. Extract the URL from the response object's url property 2. Embed the link naturally within the response text 3. Use this markdown format [Link Text](link) 4. Place links contextually where they're most relevant 5. Never assume the user can access the URL elsewhere - include it inline 6. Always put reference link if mention content from note, deal Contact Object: The contact object contains the following fields: Name, email, work experience, tags, location Tags field contains multiple single word or multi word tags that describe the industry experience of a given person When searching for contacts, generate simple queries (ideally one or two words long) based on industry or desired skill Note on seniority: When searching for contacts, please note that seniority of contacts is not stored in the database as a tag. The tags field inly contains industry tags (e.g., financial services, banking, manufacturing, etc.). For example if the user requests “senior executives” and appropriate search would be “CFO” OR “CEO”. The word “senior” or “executive” will rarely generate good results. Please use your LLM logic to judge seniority of the returned contacts, rather than specifying it as an explicit search term. Note on industry tags: When working with industry references, please consider all of the commonly used synonyms of the target industry. For example, when searching for “medtech executives”, it is useful to generate several calls for “medtech”, “medical technology” and “healthcare” and then to summarise all of the resulting contacts. Please consider relevant industry jargon for the exact user query. Note on M&A / PE jargon: Please consider the following frequently used jargon in the private equity industry: When dealing with M&A investment bankers, users will frequently refer to them as “bankers” or “advisers”. In the dataset, the contacts are rarely tagged with these tags, instead they will be saved under the tag “M&A”, “investment banking” or “corporate finance” Outside of M&A, the users will sometimes use the word “advisers” as a way to describe all advisory services that are offered in the context of a PE deal (financial DD, tax DD, commercial DD, etc.). “Senior advisers” or “industry advisers” might refer to senior execs that are associated with the fund that help them on evaluating particular deals. In the contacts database they will be stored as regular executives with some potential notes attached. Use your judgement to generate appropriate search queries depending on the context. Always specify to the user why you are using certain search terms or how you have interpreted their request. Return schema { realReturnCount: real count of returned items regardless of specified limit; count: number (all count of items in search); remainingCount: count of items that not fetched; data: array of contacts sliced by pagination; } tool can return less items than was specified in limit in such case for next request use offset = prevOffset + realReturnCount. To understand that you can fetch additional items use remainingCount filed in response if it's not 0 you can continue fetch

Return schema { realReturnCount: real count of returned items regardless of specified limit; count: number (all count of items in search); remainingCount: count of items that not fetched; data: array of deals sliced by pagination; } tool can return less items than was specified in limit in such case for next request use offset = prevOffset + realReturnCount. To understand that you can fetch additional items use remainingCount filed in response if it's not 0 you can continue fetch id in stages is value for search name in stages is possible alias that user can use Possible stages: (id: funnel, name: Top of the funnel), (id: tracking, name: Tracking), (id: due-diligence, name: Due diligence), (id: execution, name: Execution), (id: dead, name: Dead), (id: completed, name: Completed) CRITICAL INSTRUCTION: Link References in Responses When generating responses that reference external resources, documents, or objects, you MUST always include the link reference directly in the response text itself, using the URL property from the response object. Requirements: 1. Extract the URL from the response object's url property 2. Embed the link naturally within the response text 3. Use this markdown format [Link Text](link) 4. Place links contextually where they're most relevant 5. Never assume the user can access the URL elsewhere - include it inline 6. Always put reference link if mention content from note, deal

Return Notes by search string. Use only for searching notes by string. Return schema { realReturnCount: real count of returned items regardless of specified limit; count: number (all count of items in search); remainingCount: count of items that not fetched; data: array of notes sliced by pagination; } tool can return less items than was specified in limit in such case for next request use offset = prevOffset + realReturnCount. To understand that you can fetch additional items use remainingCount filed in response if it's not 0 you can continue fetch