Skip to main content
Glama

Delete an invoice's customer page

well_delete_invoice_portal_link
DestructiveIdempotent

Delete the customer page of one issued invoice: the page whose address and QR code the invoice prints, and that well_mint_payment_link gives as portal_url. After the delete, that address no longer opens for anyone, including from a PDF or a message already sent, and its card payment link is turned off at the provider. Call it only when the owner asks to delete, stop or cancel an invoice's customer page or payment link; never on your own. The invoice itself stays.

Pass invoice_id: the invoice's id, or the number the owner named it by (INV-2026-0148).

The result's outcome:

  • deleted: tell the owner the page and its address no longer open. A later well_mint_payment_link makes a new page with a new address; the deleted one never opens again.

  • no_live_link: the invoice has no customer page; say so, and never say one was deleted.

  • provider_link_kept: nothing was deleted, and message says why. Give connect_url as a plain link when it is present. Never retry on your own.

When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass workspace_id on the call.

Input Schema

NameRequiredDescriptionDefault
invoice_idYesThe UUID of the invoice to delete the customer page of. When the person named it by its reference instead (DRAFT-0007, the draft's own reference, or an issued number), pass that reference: Well resolves it, and refuses a reference that names several invoices.
workspace_idNoTarget workspace. Omit when the token authorizes one workspace. Required when it authorizes several — a write lands in exactly one workspace and this call would not say which.
conversation_idNoThe conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation.
idempotency_keyNoOptional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation.
workspace_scopeNoRestrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace.

Output Schema

NameRequiredDescriptionDefault
codeNo
mintNo
errorNo
messageNo
outcomeNo
successYes
invoice_idNo
connect_urlNo
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
newly_connectedNoTools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later.
resolved_workspaceNoThe workspace that answered, when the caller named none and the token authorizes several.
conversation_id_noteNoPresent only when the server opened a fresh lane, stating that no choice recorded earlier was read.
conversation_id_sourceNoWhere the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedOutput schema / properties / resolved_workspace / properties / name / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / resolved_workspace / properties / name / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / invoice_id / description
      Previous value: -"The UUID of the invoice to delete the customer page of. When the person named it by its reference instead (DRAFT-061, the number a draft shows, or an issued number), pass that reference: Well resolves it, and refuses a reference that names several invoices."New value: +"The UUID of the invoice to delete the customer page of. When the person named it by its reference instead (DRAFT-0007, the draft's own reference, or an issued number), pass that reference: Well resolves it, and refuses a reference that names several invoices."
  3. Added

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already flag destructiveHint and openWorldHint, and the description adds the substance behind them: the address stops opening for anyone including from already-sent PDFs/messages, the card payment link is switched off at the provider, and the invoice itself survives. It also enumerates the three outcomes and forbids autonomous retry on provider_link_kept — context an agent cannot get from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action and its blast radius, then parameter guidance, then outcome handling — a sensible order with each block earning its place. It is longer than necessary in places (the outcome bullets restate the schema's own enum), and the sentence "this read will not guess" is loose wording for a destructive write.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, open-world mutation this covers what an agent needs: effect scope, irreversibility for third parties, agent-authored vs owner-authored authorization, and per-outcome owner messaging. An output schema exists, yet the description earns its outcome guidance by prescribing what the agent should tell the owner.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description still adds value by showing that invoice_id accepts an owner-named reference (INV-2026-0148) and by explaining the single-vs-multi workspace rule for workspace_id. It adds nothing about conversation_id, idempotency_key, or workspace_scope, so it is not fully additive.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Delete the customer page of one issued invoice") and pins down exactly which page: the one whose address and QR code the invoice prints, produced by well_mint_payment_link. That distinctness from well_delete_invoice ("the invoice itself stays") and well_delete_invoice_draft_link is explicit, so an agent can route without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit gate: "Call it only when the owner asks to delete, stop or cancel an invoice's customer page or payment link; never on your own." It also resolves the workspace ambiguity rule (single-workspace token = call directly; multi = pass workspace_id), which is the other decision an agent must make before calling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources