- Category: documents
- Auth: DCR_OAUTH
- Composio-managed OAuth available? No
- Tools: 22
- Triggers: 0
- Slug:
PANDADOC_MCP - Version: 20261018_00
Tools
Documents archive
Documents archive
Documents audit trail get
Documents audit trail get
Documents content get
Documents content get
Documents create
Documents create
Slug: Examples:
PANDADOC_MCP_DOCUMENTS_CREATECreate document
Create a new PandaDoc document. Pass a singlerequest object and set its source to choose how the document is created:source: "template"— from an existing template. Required:template_uuid. Also acceptsname,recipients,fields,tokens,metadata,tags,images,pricing_tables,tables,texts,folder_uuid,owner,detect_title_variables,content_placeholders.source: "markdown"— from markdown content. Required:name,document_markdown. Also acceptsrecipients(individual recipients only; groups are not supported),role_fields,folder_uuid.source: "file"— from a downloadable PDF or DOCX file URL. Required:name,url. Also acceptsrecipients,parse_form_fields,fields,tokens,metadata,tags,folder_uuid,owner.
source: each source accepts only its own parameters. Passing a parameter that belongs to another source is rejected by validation, so you never need to guess which fields are ignored.Not for editing an existing document — use documents_update for that.Asynchronous creation
Document creation is asynchronous for everysource (template, markdown, and file).A successful tool response means creation was accepted, not that the document is ready. The document starts in Uploaded and becomes Draft once it is ready.After calling this tool:- Poll
documents_status_getuntil it reportsDraft, or until it returns an error. - If
Draft, the document is ready to edit, send, or fetch details/content. - If
documents_status_getreturns an error, creation failed (invalid file, markdown conversion failure, validation errors, etc.). Reporterror.detailand do not call details/content/edit/send on it. This is terminal —error.retryableisfalse, so stop polling. - While status is still
Uploaded, do not assume success and do not call tools that require a ready document.
Template
Create a document populated from an existing PandaDoc template. Requirestemplate_uuid. Recipients are optional — omit them to use template defaults or to add them later. If the template isn’t known yet, call templates_list first, then templates_details_get to discover its roles, fields, and variables. Optionally set fields, tokens, pricing tables, recipients, and other template data.File
Create a document from a PDF or DOCX file referenced byurl. The URL must be directly downloadable (no auth, no HTML interstitials) — presigned S3/GCS/Azure URLs or direct CDN links work best; Google Drive and Dropbox share links do not (they return HTML, not the file).To parse fillable PDF form fields, set parse_form_fields: true and provide fields mapping every form field name to a recipient role — omitting any causes failure.Markdown
Create a new document in PandaDoc from markdown when there is only text representing the document content. Document content must be generated according to the guidelines below. The response includes adocument_url field with a direct URL to open the created document in PandaDoc.Markdown guidelines
You can use standard CommonMark and GitHub-Flavored Markdown (tables, strikethrough, etc), plus the following custom extensions:Custom Syntax Extensions
1. Variables
Variables are placeholder values that the document creator fills in PandaDoc before sending to recipients. Prioritize variables over fields for any value that the sender controls or pre-fills, even if it may be visible to recipients.Syntax:[VariableName] or [Variable.Name] or [Multi.Part.Variable]- Can include underscores, numbers, and multiple dot-separated parts
- Document metadata:
[Effective.Date],[Agreement.Number],[Contract.Value] - Company/sender information:
[Company.Name],[Company.Address] - Pre-calculated values:
[Invoice.Total],[Discount.Amount] - Recipient information already known:
[Recipient.CompanyName],[Recipient.FirstName]
2. Fields
Fields are interactive form elements that recipients fill in or interact with during the signing process. Recipients see these as input boxes, checkboxes, or signature areas.Use fields for values controlled by the recipient:- Recipient signatures:
[[signature]] - Recipient personal data they must enter:
[[text]],[[email]],[[phone]],[[date]] - Recipient choices/consents:
[[checkbox]] - Information only the recipient knows or decides
[[field_type attributes]]Field Types:text- Text input fieldemail- Email input fieldphone- Phone number input field (formatis required — see below)number- Number input fielddate- Date input fieldcheckbox- Checkbox fieldsignature- Digital signature fielddropdown- Dropdown selection field (optionis required — see below)
required="true"- Makes field requiredplaceholder="text"- Placeholder textchecked="true"- Pre-checked (checkbox only)value="timestamp"- For date fields, use UNIX timestamp with millisecond precision (e.g., value=“1718406000000”). For other fields, use plain text (e.g., value=“John Doe”).format="US"orformat="international"- Required forphonefields. Must be exactly"US"or"international". There is no default — omitting it causes a validation error.date_format="yyyy/MM/dd"- Date format in ICU notation (e.g.,"dd/MM/yyyy","MM-dd-yyyy"). Defaults to"yyyy/MM/dd"if omitted.option="Text"- Required fordropdownfields. Repeatable — add one per option (e.g.,option="Yes" option="No"). To assign a stable UUID to an option, useoption="uuid:Text"format.id="Client_Text1"- Specify an external ID that describes who should fill this field and what it represents (e.g.,id="Client_Signature",id="Landlord_FullName",id="Buyer_Email"). Use the pattern<RecipientRole>_<FieldPurpose>so the field can later be assigned to the correct recipient. Multiple fields MAY share the same ID (they’ll be synced — when one is filled, all are filled with the same value), but they MUST have the same type and attributes. This is also the only valuerole_fields[].field_idsmay reference (see below) — a field with noid="..."cannot be pre-assigned to a role.
role_fields: to pre-assign a field to a recipient’s role at creation time, give the field an id="..." in document_markdown, then reference that exact same string in role_fields[].field_ids. A field_ids value that does not match any id="..." in document_markdown is rejected — never invent a role_fields value without first setting the matching id="..." on the field:[[text placeholder="Enter name"]][[email required="true" placeholder="Email address"]][[phone format="US"]][[phone format="international"]][[number]][[date required="true" value="1718406000000"]][[date date_format="dd/MM/yyyy"]][[checkbox checked="true"]][[dropdown option="Yes" option="No"]][[dropdown option="Yes" option="No" value="Yes" placeholder="Choose..."]]
[[text id="Field1"]] and [[email id="Field1"]] in the same document as well as [[text id="Field2" placeholder="Full Legal Name" ]] and [[text id="Field2"]] because they have different attributes.Dropdown constraints:- At least one
optionattribute is required. - Option texts must be unique within the dropdown.
- If
valueis set, it must match one of the defined option texts exactly; otherwise a validation error occurs.
3. Standalone Checkboxes
Checkboxes use GFM syntax but can appear anywhere, not just in lists:[ ]- Unchecked[x]- Checked- Can be used inline, standalone, or in task lists
4. Page Breaks
Syntax:--- (three hyphens) creates a page break.IMPORTANT: Page breaks should be rare and intentional. Most documents don’t need page breaks.Only use --- when content must be on separate pages for a specific reason:- Legal/structural requirement
- Document structure demands it
---:- Between sections (use headings:
## Section Title) - As visual decoration (use blank lines)
- Simply because there’s a section transition
Limitations (Features NOT Supported)
Do NOT include:- Raw HTML, including
<br>,<u>, and<div> - Blockquotes inside lists
- Images inside links inline with text (e.g.,
[](link)) - Merged table cells
- Field types must be lowercase and match the closed set exactly (
text,email,phone,number,date,checkbox,signature,dropdown). Capitalized or otherwise altered forms are not recognized. - The only valid syntax is
[[field_type attributes]]. Forms like[[Signature|Signer]],[[signature:sig_a]],[[s:Owner1]], and[[signature_1]]are not recognized — use[[signature id="Signer_Signature"]]instead. - Fields sharing the same
idmust have the same field type — a mismatched type is rejected.signaturefields cannot share anidwith any other field, including anothersignaturefield. - Every value passed in
role_fields.field_idsmust match theidattribute of a field present indocument_markdown.
Input Parameters
Document to create. Set
source to template (create from a PandaDoc template), markdown (create from markdown content), or file (create from a PDF/DOCX file URL). Each source accepts only its own parameters.Output
Documents details get
Documents details get
Slug:
PANDADOC_MCP_DOCUMENTS_DETAILS_GETRetrieve a document’s full structure by document_id: name, status, dates, version, reference number, creator, template, recipients, fields, variables, tokens, tags, pricing/grand total, and linked objects. Use to inspect a document before acting on it. Does not return extracted metadata — use documents_metadata_batch_get for that; for the overall status only, use documents_status_get.Input Parameters
Output
Documents fields assign
Documents fields assign
Slug:
PANDADOC_MCP_DOCUMENTS_FIELDS_ASSIGNAssign, reassign, or unassign document fields to recipients. The document must be in draft status. Provide a list of field-to-recipient mappings. Set recipient_id to null to unassign a field. Use get document details to obtain field UUIDs (fields[].uuid) and recipient IDs (recipients[].id). Once a field is assigned, that recipient becomes a signer for it. If it’s unclear which recipient a field belongs to, ask the user before assigning.Input Parameters
List of field-to-recipient assignments. Each item maps a field UUID to a recipient UUID (or null to unassign).
Output
Documents list
Documents list
Slug:
PANDADOC_MCP_DOCUMENTS_LISTPaginated document listing with structured filters: status, folder, tag, free-text search, sorting, and created/completed date ranges.Examples: ‘list 50 Draft docs’ · ‘documents in folder <folder_uuid> tagged onboarding’ · ‘page 3 sorted by date_modified’For natural-language queries, prefer ai_search if available.Input Parameters
Filters documents by status. Valid values: Draft, Sent, Completed, Uploaded, Error, Viewed, Waiting for Approval, Approved, Rejected, Waiting for Payment, Paid, Expired, Declined, External Review, Scheduled.
Output
Documents metadata batch get
Documents metadata batch get
Slug:
PANDADOC_MCP_DOCUMENTS_METADATA_BATCH_GETUse to read the business terms extracted from documents — counterparty, contract value, dates, renewal terms — without fetching and re-reading their full text. Handles 1-40 documents per call, so pass a one-element document_ids for a single one. Narrow the response with field_keys when only certain terms matter. Extraction generally runs once a document is completed, so a document still being worked on may have nothing to return yet. Each document reports its own outcome, so one failure does not lose the rest: ok carries that document’s fields, extraction_pending should be retried after retry_after seconds, extraction_not_started means the document is not completed yet, extraction_failed is terminal (contact support), not_found and access_denied mean the document cannot be read, and internal_error is safe to retry for that document alone.Input Parameters
Optional case-sensitive filter on metadata field
key (the human-readable field name returned as results[].ai_metadata.results[].key, e.g. Contract value). Unknown keys are silently ignored. When omitted, every populated field is returned per document.Output
Batch metadata for up to 40 documents in a single call. Returns
{count, results[]} where each entry is keyed by document_id and discriminated by status: ok carries the populated metadata; extraction_pending carries retry_after seconds; extraction_failed is terminal (contact support); extraction_not_started typically means the document is not yet completed; not_found and access_denied are per-document gating outcomes; internal_error is an isolated per-document failure that is safe to retry on its own. Whole-request failures (validation, auth, rate limit, …) surface as a standard tool error.Documents reminder send
Documents reminder send
Slug:
PANDADOC_MCP_DOCUMENTS_REMINDER_SENDSend a reminder to recipients of a document that is out for signature, so the ones who have not completed their part are prompted again. The document must be in Sent or Viewed status. Reminders reach real people by email and/or SMS, so confirm with the user which recipients to remind before calling. Take recipient ids from the document’s details; recipients left out of the call are not reminded. To word the email yourself, pass subject and message at the top level of the call — they apply to every recipient in it. The outcome is reported per recipient and per delivery method, including the reason a reminder was not delivered.Input Parameters
Body of the reminder email, in Markdown, applied to every recipient in this call. Set this when the user dictates the wording (“text SIGN IT”). Ignored by SMS; the account default is used when omitted.
Subject line for the reminder email, applied to every recipient in this call. Set this when the user dictates a subject (“subject ASAP”). Ignored by SMS; the account default is used when omitted.
Output
Documents search
Documents search
Slug:
PANDADOC_MCP_DOCUMENTS_SEARCHFull-text search with status/date filters.Examples: ‘NDA in completed docs’ · ‘modified 2026-01-01–2026-03-31’ · ‘sent docs Q1 2026’For natural-language queries, prefer ai_search if available. If the user refers to a document by name and an ID is needed for a downstream operation, use this tool to resolve the name to an ID first. Do not ask the user for a document ID before attempting this lookup.Input Parameters
Restrict hits to documents with these statuses (omit to ignore status). Valid values: Draft, Sent, Completed, Uploaded, Error, Viewed, Waiting for Approval, Approved, Rejected, Waiting for Payment, Paid, Expired, Declined, External Review, Scheduled. Example: [“Sent”, “Completed”].
Inclusive window end (ISO-8601), e.g.
2026-03-31T23:59:59Z. Use together with date_filter_column and from_date.Inclusive window start (ISO-8601), e.g.
2026-03-01T00:00:00Z. Use together with date_filter_column and to_date.Which document timestamp the date window applies to. If you set any date filter, set all three of
date_filter_column, from_date, and to_date. Allowed values: date_created, date_expiration, last_modified, signature_date, effective_date.Output
Documents send
Documents send
Slug:
PANDADOC_MCP_DOCUMENTS_SENDSend a document to its recipients. The document must be in Draft status. After sending, the status changes to Sent and recipients receive a notification. Use skip_unfilled_variables to send even when some variables are empty. Always confirm with the user before sending.Input Parameters
If true, disables email notifications for document recipients and the sender. Also disables scheduled reminders. Does not affect ‘Approve document’ email notification.
Configuration for selecting approvers from approval workflow groups. Copy ‘steps’ from the ‘approval_execution’ section of Document Details and set ‘is_selected’ to true for the desired approver.
Settings for document and signature forwarding. Controls whether recipients can forward the document or reassign their fields to another person.
Must be false by default. Only set to true when the user has explicitly chosen to send with empty variables.
Output
Documents status change
Documents status change
Slug:
PANDADOC_MCP_DOCUMENTS_STATUS_CHANGEManually change a document’s status. Only these transitions are allowed: Completed, Paid, Expired, or Declined. Status changes are restricted based on the current document status. Other statuses (such as Sent, Viewed, Approved) are set automatically by the system and cannot be set with this tool.Input Parameters
Output
Documents status get
Documents status get
Slug:
PANDADOC_MCP_DOCUMENTS_STATUS_GETRetrieve the overall document status (e.g. Draft, Sent, Completed, Expired). Some statuses are set automatically by the system: Sent (when the document is sent), Viewed (when a recipient opens it), Approved/Rejected (via approval workflows). For per-recipient signing progress use documents_details_get. Right after creating a document it may still be processing — if so, wait briefly and check again before acting.Input Parameters
Output
Documents summary get
Documents summary get
Slug:
PANDADOC_MCP_DOCUMENTS_SUMMARY_GETReturns a summary for the specified document. Supports three granularity levels: detailed, short, or headline. If not ready, returns {retry_after: N} where N is seconds to wait before retrying.Input Parameters
Summary granularity to return. Must be one of: ‘detailed’, ‘short’, or ‘headline’.
Output
Documents update
Documents update
Slug:
PANDADOC_MCP_DOCUMENTS_UPDATEUpdate a document. Document must be in Draft status. You can update text blocks, fields, and other document properties. After creating a new document, wait for it to reach Draft status before updating. To modify individual recipients, use recipients_* tools — the recipients param here replaces the entire list.Input Parameters
Output
Recipients add cc
Recipients add cc
Slug:
PANDADOC_MCP_RECIPIENTS_ADD_CCAdd a CC (non-signing) recipient to a document. Requires an existing contact ID. Cannot add to Expired or Declined documents. Adding a contact that is already a CC recipient is silently ignored. This tool only adds CC recipients; signers must be set via documents_create or documents_update.Input Parameters
Output
Recipients delete
Recipients delete
Recipients edit
Recipients edit
Slug:
PANDADOC_MCP_RECIPIENTS_EDITUpdate one recipient’s details (email, name, phone, company, address, redirect) in place. Signers can be edited in Draft, Waiting Approval, Approved, Rejected, Sent, or Viewed status. A signer’s email cannot be changed after they have signed. CC recipients can be edited in any status except Expired or Declined. Get recipient_id from document details first. Cannot use emails of existing contacts — use recipients_reassign for that.Input Parameters
Output
Recipients reassign
Recipients reassign
Templates create
Templates create
Templates details get
Templates details get
Slug:
PANDADOC_MCP_TEMPLATES_DETAILS_GETInspect a template’s schema — roles, fields, variables, pricing tables, content placeholders, tags, metadata — usually to prepare a documents_create call (e.g. ‘what roles does the Sales Contract template expect?’). Typical flow: templates_list -> this tool -> documents_create. Not for listing templates or fetching a regular document.Input Parameters
Output
Templates list
Templates list
Slug:
PANDADOC_MCP_TEMPLATES_LISTDiscover, browse, or pick a template by name, tag, or folder (e.g. ‘what templates do we have?’, ‘find the NDA template’). If the user refers to a template by name and an ID is needed for a downstream operation, use this tool to resolve the name to an ID first. Do not ask the user for a template ID before attempting this lookup. Returns a paginated list of templates. Pass a returned id as templates_details_get’s template_id to inspect roles/fields/variables, or as documents_create’s template_uuid to generate a document. Not for searching documents (use documents_list) or creating one.Input Parameters
Returns only the shared templates.