bulk-update-faxes
ChatGPTUpdate multiple fax records in one request (is_read and/or comment). Side effects: modifies multiple fax records.
bulk-update-outbox-faxes
ChatGPTUpdate comment for multiple queued outbox faxes in one request. Side effects: modifies multiple outbox records.
create-contact
ChatGPTCreate a new contact in Fax.Plus address book. Requires name and fax_number (E.164, e.g. +15551234567). Optional groups must be group names (e.g. Vendors), not group IDs. Side effects: creates contact; optional shared discloses it to corporate members.
create-contact-group
ChatGPTCreate a contact group (Fax.Plus tag) to organize contacts. When assigning contacts via set-contact-groups / create-contact / update-contact, pass this group's name, not its id. Side effects: creates contact group; optional shared discloses it to corporate members.
delete-contact
ChatGPTDelete a contact. This is destructive and requires explicit confirmation. Side effects: deletes contact.
delete-contact-group
ChatGPTDelete a contact group (Fax.Plus tag). This is destructive and requires explicit confirmation. Side effects: deletes contact group.
delete-fax
ChatGPTDelete a fax record. This is destructive and requires explicit confirmation. Side effects: deletes fax record.
delete-outbox-fax
ChatGPTDelete a queued outbox fax record. This is destructive and requires explicit confirmation. Side effects: deletes outbox fax record.
get-fax
ChatGPTGet details for a specific fax record. A 404 immediately after send-fax-uploaded can mean the record is not visible yet, not that the send failed. Side effects: none (read-only).
get-fax-report
ChatGPTReturn a short-lived URL for the fax confirmation report (PDF). Save that URL to a file on disk immediately. Do not paste the report bytes into the conversation. Open the saved PDF when the user wants to view it. Side effects: none (read-only); returns url and expiration_seconds, not file bytes.
get-fax-thumbnail
ChatGPTRetrieve a fax thumbnail image. Side effects: none (read-only); returns base64 image bytes in structured output.
get-file
ChatGPTReturn a short-lived URL for a sent or received fax file (pdf or tiff). Save that URL to a file on disk immediately. Do not paste the file bytes into the conversation. Open the saved file when the user wants to view it. Side effects: none (read-only); returns url and expiration_seconds, not file bytes.
get-file-page
ChatGPTReturn a short-lived URL for one fax page as a one-page PDF. Save that URL to a file on disk immediately. Do not paste the page bytes into the conversation. Open the saved PDF when the user wants to view it. Side effects: none (read-only); returns url and expiration_seconds, not file bytes.
get-member-details
ChatGPTGet a corporate member's role and faxing quota. Side effects: none (read-only).
get-number
ChatGPTGet information about a specific fax number. Side effects: none (read-only).
get-outbox-fax
ChatGPTGet details of a fax scheduled for sending (outbox). A 404 immediately after send-fax-uploaded can mean the record is not visible yet, not that the send failed. Side effects: none (read-only).
get-plan
ChatGPTGet the plan type and admin/owner flags for a user. Side effects: none (read-only).
get-token-info
ChatGPTGet metadata about the current access token (type, scopes, expiration, etc.). Side effects: none (read-only).
get-user
ChatGPTGet account information for a user. Side effects: none (read-only).
list-contact-groups
ChatGPTList contact groups (Fax.Plus tags) with optional pagination and filters. Side effects: none (read-only).
list-contacts
ChatGPTList contacts with optional filters (name, fax_number, groups, note), pagination, sorting, and shared/personal filter. Use name=Jane (or fax_number=...) to filter; do not list everything and filter client-side. When sending a fax, always call this after pipeline_start and list-numbers (optional pipeline_id; use limit 20) before request-file-from-user. Do not ask the user for a contact. Response groups are group names (API stores IDs; this tool resolves them). Side effects: none (read-only).
list-faxes
ChatGPTList fax records for a user. Returns paginated results. Side effects: none (read-only).
list-members
ChatGPTList all corporate members in your account. Side effects: none (read-only).
list-numbers
ChatGPTList your purchased or assigned phone numbers. When sending a fax, always call this after pipeline_start (optional pipeline_id) before request-file-from-user. Do not ask the user to pick a number. Side effects: none (read-only).
list-outbox-faxes
ChatGPTList faxes in the outbox that are waiting to be sent. Side effects: none (read-only).
pipeline_start
ChatGPTStarts a new pipeline and returns its pipeline_id. Call this first when sending a fax; pass the returned id to every subsequent pipeline tool, and optionally to list-numbers / list-contacts. Side effects: none (mints a handle; writes no state).
request-file-from-user
ChatGPTCall pipeline_start first, then list-numbers and list-contacts (limit 20), then this tool — always that order. Pass pipeline_id here unchanged. Pass numbers from list-numbers and contacts from list-contacts on this call so the UI can show pickers. Do not re-list inside this tool. Do not ask the user for a sender or destination. Pass optional to/from only if the user already named a number or contact (prefill); omit them otherwise. Prefill to is an array of {number, optional name}; include name when the destination is a contact. from is a number only. Never ask the user to attach the file in chat, and never expect the document to arrive as a chat attachment. NEVER read file contents and NEVER pass base64 or file bytes. Always pass start_file_upload=true and the same pipeline_id. Returns one of three chat payloads. MCP Apps (no mode): widget token in structuredContent; the UI uploads and sends. Do not call send-fax-uploaded or upload-file. mode=unconfirmed: client did not announce Apps support. Relay the user notice, continue as if the UI is present, and use the curl recipe in the same payload only after the user confirms no panel appeared. mode=agentic: client has no Apps support. Follow the curl recipe (POST fax_file), then call send-fax-uploaded with the returned path. Never paste file bytes or base64. The UI does not send a chat message when it sends the fax; it adds the submitted fax ids to the conversation context. When a fax_id is known, call get-fax or get-outbox-fax. Side effects: mints a short-lived fax-scoped access token; opens the upload UI when the client supports MCP Apps, and that UI uploads the file and sends the fax to the chosen recipient numbers when the user clicks Send.
resend-fax
ChatGPTQueue a new outbound fax by reusing an existing fax file reference via from_fax. to must be an array of destination numbers. Side effects: queues outbound fax for delivery.
send-fax-uploaded
ChatGPTQueue a new outbound fax using storage paths. Call this after an agentic request-file-from-user curl (files = path from the files POST JSON) or after upload-file. Do not call this after the MCP Apps UI flow — the widget already sent. Pass paths here with to/from and optional send_time. Do not pass local filesystem paths or file bytes. to must be an array. The same paths may be reused for multiple sends. Success means queued/submitted only—not delivered. Status can be checked with get-fax or get-outbox-fax using the returned id. Side effects: queues outbound fax for delivery.
set-contact-groups
ChatGPTAssign contacts to contact groups (Fax.Plus tags). Pass group names (e.g. Vendors), not group IDs from create-contact-group. This overwrites previous group assignments for the selected contacts. If a model passes a group ID by mistake, this tool resolves it to the group name before calling the API. Side effects: updates contact-group associations; optional shared discloses them to corporate members.
share-contact-groups
ChatGPTShare selected personal contact groups (tags) with corporate members in your organization. Side effects: shares contact groups to corporate scope.
share-contacts
ChatGPTShare selected personal contacts with corporate members in your organization. Side effects: shares contacts to corporate scope.
update-contact
ChatGPTPartially update an existing contact. Omit fields you want to keep; only set fields to change. The Fax.Plus API uses PUT (full replace), so this tool loads the contact, merges your fields, and writes the full record back - omitted fields are preserved. If setting groups, use group names (e.g. Vendors), not group IDs. Side effects: modifies contact.
update-contact-group
ChatGPTUpdate a contact group (Fax.Plus tag). Side effects: modifies contact group.
update-fax
ChatGPTUpdate a fax record's read state and/or comment. Side effects: modifies fax record metadata.
update-number
ChatGPTAssign a fax number to a corporate member (adds them to assigned_to). user_id is the number owner/account context (usually self for the admin). payload.assigned_to is the member user ID to assign TO. Side effects: adds a member to the number's assigned_to list and notifies them by email and push.
update-outbox-fax
ChatGPTUpdate a queued outbox fax (comment only). Side effects: modifies outbox record metadata.
upload-file
ChatGPTUpload document bytes as base64, then call send-fax-uploaded with the returned path. Side effects: stores file for fax delivery.
bulk-update-faxes
Claudebulk-update-outbox-faxes
Claudecreate-contact
Claudecreate-contact-group
Claudedelete-contact
Claudedelete-contact-group
Claudedelete-fax
Claudedelete-outbox-fax
Claudeget-fax
Claudeget-fax-report
Claudeget-fax-thumbnail
Claudeget-file
Claudeget-file-page
Claudeget-member-details
Claudeget-number
Claudeget-outbox-fax
Claudeget-token-info
Claudeget-user
Claudelist-contact-groups
Claudelist-contacts
Claudelist-faxes
Claudelist-members
Claudelist-numbers
Claudelist-outbox-faxes
Clauderesend-fax
Claudesend-fax-uploaded
Claudeset-contact-groups
Claudeshare-contact-groups
Claudeshare-contacts
Claudeupdate-contact
Claudeupdate-contact-group
Claudeupdate-fax
Claudeupdate-number
Claudeupdate-outbox-fax
Claudeupload-file
Claude