Introw PRM

Read KPI and goal progress for a partner. Use this when the user asks about a partner's goals, KPIs, targets, progress, achievement status, or goal performance for a specific period. Requires a partnerId or partner context. Optionally accepts a date range for the goal progress period. Returns the partner goal/KPI records with calculated progress from Introw and CRM-synced data.

get_partner_goals

Read configured partner tiers and tier plan information for the authenticated organisation. Use this when the user asks about partner levels, tier names, tier order, requirements, rewards, benefits, or how partners progress between tiers. Returns tiers ordered by their configured order, including tier name, tier properties, badge image URL, and tier plan/group name for admins.

get_partner_tier_information

Browse the asset library's folder tree: how content is organised, what is in each folder, and where a new asset or subfolder should go. Use this before upsert_asset (to file an asset in the right folder) and before upsert_asset_folder (to find a folderId, or to check whether a folder already exists under a different name). Prefer reusing an existing folder over creating a near-duplicate. Returns per folder: folderId, name, path (the readable location such as "Sales/Battlecards"), parentFolderId, partnerId, categories, assetCount (assets directly inside), subfolderCount, and archived plus archiveReason when archived folders are included. Filter with query (name), parentFolder (only what is inside that folder, at any depth), partnerId (a partner's private library), includeAllPartnerFolders, and includeArchived.

list_asset_folders

List the authenticated organisation's asset library: documents, images, videos and URL/embed assets, plus the library's folders. Use this to find an assetId before updating an asset with upsert_asset, to find a folderId to file a new asset under, to check which categories are in use, or to answer "what do we have on X?" about library contents (use find_relevant_content when the question is about what a document *says*). Filter with query (name/file name/description), folder, or partnerId for a partner's private library. Returns per asset: assetId, name, description, fileName, mimetype, type (FILE or URL), folder, categories, isPublic, locale, viewCount and timestamps.

list_assets

List the authenticated organisation's LMS certificates. Use this to find a certificateId to link a certificate to a course via upsert_course (awarded when a learner passes the course), or to answer how many partners/learners currently hold each certificate. Returns per certificate: id, name, description, validity fields, activeLearnerCount, activePartnerCount (non-expired awards), and linkedCourses (courses that award this certificate). Certificates themselves (design, colors, badge) are created and edited in the Introw UI, not through MCP. Use list_issued_certificates when the user asks *who* holds a certificate.

list_certificates

List learners enrolled in the organisation's LMS courses, including progress and completion. Use this when the user asks who is enrolled, in progress, or has completed a course, or wants a roster of partners/learners per course. Filter by courseId (from list_courses), partnerId, status (NOT_STARTED, IN_PROGRESS, COMPLETED), or a free-text query on learner/partner/course name. Returns per enrollment: enrollmentId, courseId, courseName, partnerId, partnerName, learnerId, learnerName, learnerEmail, status, enrolledAt, startedAt, completedAt, and module progress counts. For certificate awards (which can also be given without completing a course), use list_issued_certificates. For per-course totals without a roster, use list_courses.

list_course_enrollments

List the authenticated organisation's LMS courses. Use this to find a courseId before calling upsert_course, to check import status after creating/updating a course with a SCORM package, or to answer how many partners/learners are enrolled or have completed each course. Returns per course: id, name, description, lmsMode (NATIVE or SCORM_RUNTIME), scormStatus ("processing" while a new SCORM import is being extracted, "ready" once live, null for native courses), scormPackageVersion (opaque id of the live package), scormVersion, bannerImage, dueDate, minimumPassingScore, autoEnrollmentEnabled, isRequired, certificateId, certificateName, enrolledLearnerCount, completedLearnerCount, enrolledPartnerCount, completedPartnerCount, and timestamps. Note: after a package *replacement* scormStatus stays "ready" (the old package serves until the swap completes) — poll until scormPackageVersion changes to confirm the new package is live. Use list_course_enrollments when the user asks *who* enrolled or completed a course, and list_issued_certificates when they ask who holds a certificate.

list_courses

List partners and learners who have been awarded an LMS certificate in the authenticated organisation. Use this when the user asks who is certified, which partners/learners hold a certificate, or wants a roster of certificate holders. Filter by certificateId (from list_certificates), courseId (the certificate linked to that course), partnerId, a free-text query on learner/partner/certificate name, or includeExpired (default false, active awards only). Returns per award: issuedId, certificateId, certificateName, partnerId, partnerName, learnerId, learnerName, learnerEmail, issuedAt, expiresAt, and status (ACTIVE or EXPIRED). Course completion is tracked separately. Use list_course_enrollments for who finished a course, and list_courses / list_certificates for counts without a roster.

list_issued_certificates

Gather source data for a partner business review. Use this when the user asks to prepare a QBR, MBR, WBR, or similar partner review for one partner. Requires partnerId and duration. QUARTERLY reads data from three months back through three months forward, MONTHLY reads one month back through one month forward, and WEEKLY reads one week back through one week forward. Returns grouped review inputs: goals, CRM opportunities/deals, mutual action plan tasks, form submissions, and instructions for composing an agenda and discussion points. It does not create or save a meeting record.

prepare_partner_business_review

Accept, decline, or return a pending partner form submission such as a deal registration or shared lead. Use this only when the user explicitly asks to accept/approve, decline/reject, or return a specific submission, and after confirming the decision. Use search_form_submissions first to discover the submission and its formSubmissionId. ACCEPT approves the submission (recording the current approval step for multi-step approvals, finalising once all steps are approved); optionally provide linkWithDealId to link to an existing CRM deal instead of creating a new record. DECLINE terminally rejects it. RETURN sends it back to the submitter to revise and resubmit. Only pending submissions can be processed. Provide an optional message to communicate the decision to the submitter.

process_form_submission

Find CRM-synced objects in the authenticated organisation. Use this when the user asks for deals, opportunities, forecasts, tickets, cases, leads, companies, accounts, or contacts. Supports filtering by CRM object type, partner, text query, deal stage, due/overdue/inactive deal views, rolling date periods, explicit date ranges, and sorting/limits such as top deals by amount or earliest close date. Returns matching objects with formatted properties, related partner summary when available, recent activity for each object, stage metadata, currency, timezone, integration metadata, and an object link when a URL context is available. Map common terms before calling: opportunity or forecast to DEAL, account to COMPANY, and case to TICKET. Provide objectOfInterestPlural as the user's plural label for the object type, such as "deals", "tickets", "companies", or "contacts".

search_crm_objects

Find partner form submissions in the authenticated Introw organisation. Use this when the user asks about submitted partner forms, deal registrations, shared leads, pending submissions, accepted submissions, declined submissions, or submissions from a specific partner. Requires a status filter: SUBMITTED for all submitted forms regardless of review status, or PENDING, ACCEPTED, or DECLINED for review state. Optionally filter by partner and created or completed date range. Returns submission data, review status, the formSubmissionId (use it with process_form_submission to accept/decline/return), submitter email/name/job title, submitter partner name, potential channel conflict flag, and a submission link when a URL context is available.

search_form_submissions

Find partner portal timeline activity in the authenticated organisation. Use this when the user asks about partner activity, engagement history, portal visits, comments, form events, task events, CRM object updates, commission events, quote events, announcements, or asset views. Supports filtering by activity type, partner, created date range, or a specific CRM object ID and type. Returns up to 500 newest timeline events with event type, created date, partner ID/name, CRM object reference, task ID, form submission ID, quote metadata, comment content, asset name, initiator metadata, and CRM object changelog fields when present.

search_partner_activity

Find public partner portal tasks in the authenticated Introw organisation. Use this when the user asks about tasks, to-dos, onboarding tasks, mutual action plan items, pending work, completed work, or tasks for a specific partner. Supports filtering by task status, partner ID, and created or completed date range. Returns matching task IDs, titles, status, due date, completion date, assignee label, description HTML, and a task link when a URL context is available.

search_partner_tasks

Find partner companies in the authenticated Introw organisation. Use this when the user asks for partner records, partner IDs, partner owners/managers, champion email, lifecycle phase, tier, experience/template, categories, country, or last activity. Returns matching partners with IDs, names, categories, country, champion email, owner/manager details, lifecycle phase, tier and tier plan, experience name, last activity date, and a partner link when a URL context is available. Use query when the user names a partner. Use dateRange only when the user asks for partners created or active within a specific period.

search_partners

Discover or submit any partner portal form for a known partner. Use this when the user wants to submit, fill out, complete, or start any partner form: registering a deal, sharing a lead, requesting MDF / funds, onboarding, feedback or surveys, submitting a project, filing a claim, applying, or any other configured partner form. This tool has two modes. Discovery mode uses partnerId, objectType, and callToAction without formId to identify the matching available form and return field IDs, labels, types, required flags, allowed dropdown options, auto-filled values, and a manual form link. Submit mode uses formId and userProvidedData from discovery to validate and submit the form. Also use this tool to change an existing CRM record when update_crm_object_properties answered with a ctaFormFallback: call it with that action's submitPartnerFormArguments (formId plus relatedObjectId and relatedObjectType), which preselects the record in the form's CRM object picker so the submission updates it instead of creating a new one. Submit mode creates a persisted form submission, may trigger configured form automations such as CRM-facing record creation, and may enqueue form, timeline, acceptance, or notification jobs. Call submit mode only after the user has provided the required form data and confirmed they want to submit it.

submit_partner_form

Update editable properties on a CRM-synced object in Introw. Use this only when the user explicitly asks to change fields on a specific deal, ticket, lead, company, or contact. Never use this tool to add a comment, note, message, or approved draft to an object, including requests phrased as "add it to the deal"; use add_partner_comment instead. Use search_crm_objects first when objectId and objectType are not already known. Provide propertiesToUpdate as CRM property API names mapped to the requested values, and include only properties the user explicitly wants changed. The tool verifies the object is linked to a partner room, checks the object's configured CRM entity list, filters to properties that are editable in Introw, normalizes values, and applies the edit. Successful edits may sync to the connected CRM. If the requested properties are not editable inline, the response may include a ctaFormFallback: the organisation routes those changes through a partner form (an "edit" or "move to next stage" button on the portal). Never report the change as impossible before checking for it. Pick the listed action that IS the requested change (never an unrelated one), then call submit_partner_form with that action's submitPartnerFormArguments to read the form's fields, and again with the same arguments plus userProvidedData to submit it; the record is already attached. A response carrying addCommentFallback instead means nothing can apply the change, and the suggestion can be posted with add_partner_comment after user confirmation.

update_crm_object_properties

Update one partner management field for one or more partners in Introw. Use this only after the user explicitly asks to set, clear, add, or remove a supported partner field and the target partner IDs are known from search_partners or prior context. Supported fields are tier, phase, experience/template, commission plan, champion email, currency, locale/language, categories, company name, and company domain. For configured option fields, the tool resolves the provided value against live Introw options and returns a needs_value, option_not_found, or ambiguous_value status when it cannot safely update. For categories, mode controls whether values are set, added, or removed. Some updates, such as tier, may also sync mapped values to the connected CRM.

update_partner_fields

Update an existing partner portal task. Use this only when the user asks to edit a task title, description, due date, status, or assignment, or to mark a task complete. Use search_partner_tasks first when the task ID is not already known. Provide taskId and only the fields the user explicitly wants changed; omitted fields remain unchanged. Use status DONE to mark a task complete. Assignment changes may enqueue an assignment notification; completion changes may enqueue a completion notification; noticeable changes record a TASK_UPDATED timeline event.

update_partner_task