Integration details
Description
LegalZoom Virtual Mail digitizes your business and personal postal mail and now you can find, understand, and manage it directly in ChatGPT. Ask about new or unread mail, search for specific items, and read or summarize scanned documents. You can also organize mail with folders and tags, review mailbox status and alerts, and check the progress of mail-handling requests. What you can do: • Find mail by sender, recipient, date, status, tag, or content • Read and summarize scanned mail • Request eligible items to be opened and scanned • Archive, organize, or securely shred eligible mail • Track shipments and available check-forwarding activity A LegalZoom Virtual Mail account is required. Some features depend on your account, plan, verification status, and the actions available for each mail item. Physical mail requests may require processing time.
- Integration type
- Plugin
- Verification status
- Not applicable
- Platform
- ChatGPT
- Primary Subcategory
- Pending
- Secondary Subcategories
- None listed
- Brand
- LegalZoom
- Access
- Account required
- First tracked
- 2026-08-25
- Tool count
- 28
- Geography
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
ChatGPT Plugin Discovery Score
ChatGPT Plugin discovery is coming soon
ChatGPT can surface a Plugin when it matches a user's request.Your Plugin Discovery Score measures how often yours appears.
No spam. Unsubscribe any time.
What discovery looks like
Competitive lineup
28 tools agents can invoke
Apply one or more existing tags to one or more mail items, and optionally remove tags in the same call. Use when the user wants to label or categorize mail with tags that already exist. Do not use it to create new tags (use create_mail_item_tag), delete tags (use delete_mail_item_tags), or to filter mail by tag (use list_mail_items). Requires pmb (from list_inboxes), mail_item_ids (from list_mail_items), and at least one of set_tag_ids or remove_tag_ids (from list_tags). Side effect: adds the given tags to those items and removes the specified ones.
Cancel a pending scan request for one or more physical mail items before the mailroom acts on it. Use when the user wants to stop a scan that is still cancellable. Do not use it to request a scan (use request_mail_items_scan) or to read scanned contents (use get_mail_item_text). Requires pmb (from list_inboxes) and mail_item_ids (from list_mail_items). Each item is checked first: cancellation occurs only where it is an available action, and items with no pending scan, a completed scan, or an archived state are skipped with a reason. Side effect: cancels the queued scan operation for eligible items.
Cancel a pending shred request for one or more physical mail items before the mailroom destroys them. Use when the user wants to stop a shred that is still cancellable. Do not use it to request a shred (use request_mail_items_shred) or to move items to TRASH (use move_mail_items). Requires pmb (from list_inboxes) and mail_item_ids (from list_mail_items). Each item is checked first: cancellation occurs only where it is an available action, and items with no pending shred, an already completed shred, or a shipped state are skipped with a reason. Side effect: cancels the queued shred operation for eligible items.
Create a new tag (label) on an inbox so it can be applied to mail items. Use when the user wants a tag that does not yet exist. Do not use it to apply an existing tag (use apply_mail_items_tags), to filter by tag (use list_mail_items), to delete a tag (use delete_mail_item_tags), or to rename tags (not supported). Creating a label that already exists on the inbox fails. Requires pmb (from list_inboxes) and label. Returns the new tag's id and label. Side effect: creates a new tag on the inbox.
Delete one or more tags from an inbox, which also removes them from any mail items that currently carry them. Use when the user wants to remove or clean up tags they no longer need. Do not use it to merely take a tag off specific items while keeping the tag (use apply_mail_items_tags with remove_tag_ids) or to create tags (use create_mail_item_tag). Requires pmb (from list_inboxes) and tag_ids (from list_tags). Every tag_id must currently exist on the inbox; if any is unknown the whole request fails and nothing is deleted. Side effect: permanently deletes the tags and detaches them from all items on the inbox.
Retrieve the check deposit(s) opened from one or more mail items: item and request statuses, check amounts, request timing and expedited handling, the destination bank account, shipment details for the physical checks, and the post-deposit operation. Use when the user asks whether the check on a specific piece of mail was deposited or about its deposit status — "was this check deposited?", "what's the deposit status for this letter?", "where did the check on this item go?" Do not use it to browse a mailbox's mail (use list_mail_items), to fetch a mail item's own metadata (use get_mail_item), or to list every deposit in an inbox (not supported). Requires pmb (from list_inboxes) and mail_item_ids (from list_mail_items). Returns one entry per requested item that has a deposit; a mail item with no deposit contributes nothing. Read-only.
Get the profile of the currently authenticated user (the caller): user ID, first and last name, email, username, daytime phone, and account creation date. Use to identify who you are acting for or to answer questions about the caller's own account. This is the person calling, not an inbox owner — the account behind an inbox is available from list_inboxes. Read-only.
Look up the authoritative meaning of a status, flag, enum, or concept returned by this MCP server, such as a mail item's digital_status or check_status. Do not use it to fetch customer data or the underlying result (use the relevant data tool, e.g. get_mail_item). The optional topic identifies a reference entry such as mail_item.digital_status. When topic is omitted, the tool returns an index of available topics; when topic is provided, it returns the raw values, short labels, and explanations for that topic. Read-only.
Return a one-call summary of an inbox and its account: current mail counts, operations in progress, account standing, usage for the current billing period, and active alerts. Alerts may include account notices, an expiring or expired payment method, and USPS Form 1583 or address-authorization issues. Use for general inbox overview or account-health questions. Do not use it to retrieve the actual mail items (use list_mail_items); usage figures are counts, not dollar amounts. Requires pmb (from list_inboxes). Read-only.
Retrieve full details for one or more mail items by ID: metadata (sender, received date, mail type, physical/scan/check status, flags, storage info, current folder, pdf and envelope urls — links expire in ~60 min) and, for already-scanned items on AI-features accounts, the AI-derived categorization (document type e.g. "Bank Statement" and a short summary). Use when you already have mail_item_ids (typically from list_mail_items) and need their complete state or a quick sense of what each piece is. Do not use it to search or list items (use list_mail_items), or to get the verbatim OCR text (use get_mail_item_text). Requires pmb (from list_inboxes) and mail_item_ids (from list_mail_items). Categorization is returned only for scanned items on AI-features accounts; metadata is always returned. Read-only.
Generate temporary, pre-signed links to the envelope/exterior photos of one or more mail items when the user wants to see what an unopened piece of mail looks like from the outside, including before any scan exists. Also use this to refresh envelope_small_url/envelope_large_url once a previously fetched link (e.g. from get_mail_item) has expired. Do not use it to view the scanned document contents (use get_mail_item_pdf_url for the scanned PDF, or get_mail_item_text for extracted text). A link is returned only for the image sizes actually available for an item (envelope_small_url, envelope_large_url); an item with no envelope photo captured yet has both omitted. Links are temporary and expire after approximately 60 minutes; each link's expiry, when available, is returned alongside it. Requires pmb (from list_inboxes) and mail_item_ids (from list_mail_items). Read-only.
Retrieve the chronological event timeline for one mail item: received, scanned, shipped, deposited, moved, tagged. Use when the user asks what has happened to an item, its current progress, or whether it is stuck. Do not use it to get item metadata or status fields (use get_mail_item), or to read item contents (use get_mail_item_text). Requires pmb (from list_inboxes) and a known mail_item_id (from list_mail_items). Returns paginated history entries ordered chronologically, plus total_count, page, and has_next_page for paging. Read-only.
Generate temporary, pre-signed links to scanned PDF files for one or more mail items when access to the actual scanned documents is needed, rather than only extracted text. Also use this to refresh pdf_url once a previously fetched link (e.g. from get_mail_item) has expired. For reading, summarizing, or searching document text, get_mail_item_text is usually the appropriate tool. Do not use it to view the envelope/exterior appearance of a piece of mail (use get_mail_item_envelope_image_url). A link is returned only for items whose scan is available; an item that has not been scanned yet, or whose scan is still in progress, has no PDF yet, and is returned without a link. Links are temporary and expire after approximately 60 minutes; each link's expiry, when available, is returned in expires_at. Requires pmb (from list_inboxes) and mail_item_ids (from list_mail_items). Read-only.
Retrieve the OCR-extracted text of one scanned mail item. Use when the user wants to read, summarize, search, or ask questions about the item's contents. Do not use it to obtain a downloadable file (use get_mail_item_pdf_url) or item metadata (use get_mail_item). Requires pmb (from list_inboxes) and a known mail_item_id (from list_mail_items), and the item must already be scanned. Returns up to 5 pages per call using start_page and page_count, plus total_pages for paging through longer items. Read-only.
Retrieve the shipment(s) that carry one or more mail items: status, tracking number and link, carrier, rate, destination address, ship and delivery dates, and the mail items included in each shipment. Use when the user asks about the shipment or package for a piece of mail they can point to — "where's my package?", "did this letter get forwarded?", "track the shipment for this item." Do not use it to browse or search a mailbox's mail (use list_mail_items) or to fetch a mail item's own metadata (use get_mail_item); it returns shipping data, not the mail item. Requires pmb (from list_inboxes) and mail_item_ids (from list_mail_items). Returns the distinct shipments covering the requested items, deduplicated by shipment id, so several items sharing one shipment yield a single entry; a mail item that has never been shipped contributes no shipment. Read-only.
List all folders in an inbox — both the built-in system folders (Inbox, All Mail, Archive, Trash, Junk Mail) and the user-created custom folders — each with its id, name, type, and unread/total piece counts where available. Use to resolve a folder name to the id you pass as folder_id to list_mail_items or move tools. Requires pmb (from list_inboxes). Read-only.
List the virtual mail inboxes accessible to the authenticated user. Each result includes the PMB (Private Mail Box number), account name, and unread and total mail counts. The PMB returned by this tool is the inbox identifier required by tools that operate on a specific inbox. This tool does not fetch mail items, recipients, or account details. Read-only.
Search and list mail items within one inbox, filtering by recipient, folder, status, tag and/or matching free text across sender, recipient, and scanned content. Use when the user wants to find, browse, or count mail and does not have a specific item ID ("the letter from the IRS," "what came in last week," "any checks?"). Do not use it when you already have a mail_item_id (use get_mail_item) or to read one item's full text (use get_mail_item_text). Requires pmb (from list_inboxes). Returns matching items with IDs, sender, dates, and status; for already-scanned items on AI-features accounts each item also includes the AI-derived document type (e.g. "Bank Statement") and a short summary. Read-only.
List the recipients - the named people or businesses that receive mail - configured on an inbox, each with its ID and name. Use to resolve a recipient name to its ID before filtering mail by recipient or transferring mail, or when the user asks who is set up on the inbox. Do not use it to list a recipient's mail (use list_mail_items with recipient_id) or to add, rename, or remove recipients (not supported). Requires pmb (from list_inboxes). Returns the recipients on the inbox with their IDs and names. Read-only.
List the tags available on an inbox (optionally filtered by a name fragment via match_phrase), returning tag IDs and labels. Use to resolve a tag name to its ID before filtering mail with list_mail_items or applying tags with apply_mail_items_tags. Requires pmb (from list_inboxes). Results are paginated (first/after), defaulting to 20 per page. Read-only.
Mark one or more mail items as read (viewed). Use when the user wants to clear unread status or says they have handled certain mail. Requires pmb (from list_inboxes) and mail_item_ids (from list_mail_items). Side effect: marks the items read and lowers unread counts.
Mark one or more mail items as unread (not viewed). Use when the user wants to restore unread status on mail they have not dealt with yet. Requires pmb (from list_inboxes) and mail_item_ids (from list_mail_items). Side effect: marks the items unread and raises unread counts.
Move one or more mail items to a destination: the inbox, the archive, the trash, or a recipient folder. Use when the user wants to file, archive, or trash mail. Do not use it to permanently destroy physical mail (use request_mail_items_shred) or to reassign items to a different recipient (use transfer_mail_items_to_recipient). Requires pmb (from list_inboxes), mail_item_ids (from list_mail_items), and a destination_folder (INBOX, ARCHIVE, TRASH, or a numeric recipient-folder id from list_folders). Side effect: relocates the items, changing where they appear.
Echo back the given message (prefixed with "pong: ") as a health check. Use only to verify MCP connectivity and the request/response round-trip. Returns no customer data and touches no account state. Read-only.
Request that the mailroom open and scan one or more physical mail items so their contents can be read; the physical originals are kept in storage afterward. Use when the user wants unscanned mail digitized ("open and scan this," "scan the letter from the IRS"). Do not use it if the item is already scanned (scan status is available from get_mail_item), to read existing text (use get_mail_item_text), or to scan and then destroy the original (use request_mail_items_scan_then_shred). Requires pmb (from list_inboxes) and mail_item_ids (from list_mail_items). Each item is checked first: a scan is requested only for items where it is an available action, and any item that cannot be scanned (e.g. a scan is already in progress, the item is archived, or identity is not verified) is skipped and returned with a reason. Side effect: queues a staff-handled scan for the eligible items; the originals stay in storage and scanning is not instant.
Request that the mailroom open and scan one or more physical mail items and then securely shred (permanently destroy) the physical originals once scanning is complete. Use when the user wants mail digitized and the paper destroyed in one step ("scan this then shred it," "scan and shred these"). Do not use it to scan and keep the original (use request_mail_items_scan), to shred without scanning first (use request_mail_items_shred), or to read existing text (use get_mail_item_text). Requires pmb (from list_inboxes) and mail_item_ids (from list_mail_items). Each item is checked first: the operation is requested only for items where scanning is an available action, and any item that cannot be scanned (e.g. a scan is already in progress, the item is archived, or identity is not verified) is skipped and returned with a reason. Side effect: queues a staff-handled scan followed by irreversible physical destruction of the originals; scanning and shredding are not instant.
Request secure shredding (permanent physical destruction) of one or more physical mail items. Use when the user explicitly wants their physical mail destroyed ("shred these," "securely dispose of this"). Do not use it to merely hide or declutter items (use move_mail_items to TRASH, which is reversible); shredding is irreversible. Requires pmb (from list_inboxes) and mail_item_ids (from list_mail_items), and optionally post_shred_action. Each item is checked first: a shred is requested only for items where it is an available action, and any item that cannot be shredded (e.g. a shred is already in progress, it has already been shredded, or it has been shipped) is skipped and returned with a reason. Side effect: queues an irreversible, staff-handled physical destruction for the eligible items.
Reassign one or more mail items to a different recipient on the inbox. Use on multi-recipient (business) inboxes when mail was attributed to the wrong recipient and needs to be moved to the correct one. Do not use it to move items between folders (use move_mail_items) or to change a recipient's own details (not supported). Requires pmb (from list_inboxes), mail_item_ids (from list_mail_items), and the target recipient_id (from list_recipients). Returns a confirmation of how many items were reassigned. Side effect: changes each item's recipient.
How do I improve a ChatGPT Plugin's discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.