BoldTrail BackOffice

Complete task

complete_buyer_offer_task

Mark a checklist task complete. It succeeds only once the task already meets its requirements (a document attached if one is required, and no review still pending), so this is the last step, never the first. When the task has no document yet, do NOT simply ask the user to upload one. Read the task first: if it carries required_document_ids, expand them with get_transaction_checklist_task and include=required_documents to learn what is actually wanted, and say so by name. Then offer the routes that fit, without assuming which the user needs - attach a file they already have (upload it, then assign_document_to_transaction_task), or start from a matching library template found with search_library_documents, following the create_signature_package guidance when the document needs signatures. When no document should be needed at all, request_task_exemption is the honest answer.

complete_transaction_task

Turn a document that is already in the transaction into the signature package itself, so signature boxes can be placed on it and it can be sent for electronic signature. The document keeps its id, its name and its place.

convert_document_to_signature_package

Creates new buyer offer API to create new buyer offer. Call get_schema_for_buyer_offers first. Pass this account's fields as extra top-level arguments keyed by each entry's uid; they are not listed in this tool's inputSchema.

create_buyer_offer

Creates a BoldTrail BackOffice contact. Account custom fields are passed flat, one top-level key per field, keyed by the field uid. Call get_schema_for_contacts first. Pass this account's fields as extra top-level arguments keyed by each entry's uid; they are not listed in this tool's inputSchema.

create_contact

Add incoming transactions Create or update incoming transactions.<br/> Update will happen in case incoming transaction with the same `external_id` and `source_id` already exists.<br/> **Note:** if existing transaction was already *accepted* of *declined*, its updates will be ignored.

create_incoming_transaction

Use this when the user wants to send documents for electronic signature and they are not a signature package yet. You have to consult the create_signature_package guidance before this tool, - it carries the required flow and its irreversible steps. If you can load Agent Skills from this server, load the `create-signature-package` skill (`skill://create-signature-package/SKILL.md`); otherwise call guide_for_create_signature_package. Never call this tool without that guidance. Create a NEW signature package document from one or more existing documents. Returns the package's document_id, which every other signature-package tool takes as its document_id argument.

create_signature_package

Use this when the user wants to add a new deal (listing, purchase or lease) to BoldTrail BackOffice. Creates a BoldTrail BackOffice transaction (real estate deal). You have to consult the create_transaction guidance before this tool - it gives the correct status, representing sides, and the account's real, account-specific fields with their requirements. If you can load Agent Skills from this server, load the `create-transaction` skill (`skill://create-transaction/SKILL.md`); otherwise call guide_for_create_transaction. Never call this tool without that guidance. Call get_schema_for_transactions first. Pass this account's fields as extra top-level arguments keyed by each entry's uid; they are not listed in this tool's inputSchema.

create_transaction

Create a new tasks in specified transaction checklists

create_transaction_checklist_task

Create user Call get_schema_for_users first. Pass this account's fields as extra top-level arguments keyed by each entry's uid; they are not listed in this tool's inputSchema.

create_user

Permanently deletes buyer offer Permanently deletes buyer offer and all associated with it data including documents. In most of the cases updating buyer offer state to "withdrawn" is preferable to deletion.

delete_buyer_offer

Remove contact by ID

delete_contact

Delete transaction by ID

delete_transaction

Delete checklist by ID

delete_transaction_checklist

Remove taks by ID

delete_transaction_checklist_task

Remove contact from transaction

delete_transaction_contact_participant

Remove transaction's document

delete_transaction_document

Remove user from transaction

delete_transaction_user_participant

Use this when the user wants a signature package's fields filled in. Writes values into a document (signature, esign) package fillable fields. Refuses once the package is sent for signature or signed. You have to consult the fill_document_package_fields guidance before this tool. If you can load Agent Skills from this server, load the `fill-document-package-fields` skill (`skill://fill-document-package-fields/SKILL.md`)

fill_document_package_fields

Finalize transaction commissions

finalize_transaction_commissions

Get account by ID

get_account_details

Get buyer offer by ID

get_buyer_offer

Get buyer offer's document

get_buyer_offer_document

Get task by ID

get_buyer_offer_task

Get specific closed/cancelled transaction fields schema Once the transaction is closed or cancelled, it's schema is archived and remains the same even though it's updated in account settings. For active transaction this schema equals the one you get from get_schema_for_transactions

get_closed_transaction_fields_schema

Get commission plan by ID

get_commission_plan

Get contact by ID

get_contact

Get contact fields

get_contact_fields

Get contact lead sources

get_contact_lead_sources

Get contact types

get_contact_types

Get current user details

get_current_user_details

Use this when you need a signature package's fillable fields or their current values. Returns fillable package fields by document, including geometry, values and bindings. Works in any package state. First consult guide_for_fill_document_package_fields or use skill://fill-document-package-fields/SKILL.md.

get_document_package_fields

Identify the source documents and their page ranges within a multi-page document package. Use when `has_package` is true. A package may preserve the boundaries of the separate documents from which it was built and identify appended e-sign audit trail pages. Each range gives the source document's name with its first and last page in the package; the range named `e-sign audit trail` is the pages added after signing. Refused when the boundaries cannot be determined.

get_document_page_ranges

Get document rejection reasons

get_document_rejection_reasons

Called by the Document viewer app, never by you. Returns document metadata and a temporary file URL.

app__get_document_viewer_data

Get email templates

get_email_templates

Returns approved clauses for one document package field. Fields with clauses include clauses_count in get_document_package_fields.

get_field_clauses

Get General Ledger Transaction by ID

get_general_ledger_transaction

Get incoming transaction by ID

get_incoming_transaction

Get onboarding checklist assignees

get_onboarding_checklist_assignees