stripe.stripe_api_write

Parameters schema

{
  "type": "object",
  "required": [
    "stripe_api_operation_id",
    "parameters"
  ],
  "properties": {
    "parameters": {
      "type": "object",
      "description": "Parameters for the API call. Include path parameters (e.g. 'customer' for /v1/customers/{customer}), query parameters, and body parameters as a flat object. Nested object fields use dot-notation (e.g. \"address.city\"). Array fields (e.g. line_items) must be passed as a JSON array value, not as a plain string."
    },
    "human_confirmation": {
      "type": "object",
      "properties": {
        "approval_token": {
          "type": "string",
          "description": "The ID of the approval token for the request. This is required on only the post-human-confirmation invocation. An example ID is `approval_123`."
        }
      },
      "description": "This tool might require human confirmation. To run it, first invoke it with the desired parameters, ignoring the `approval_token` parameter.\nIf it requires human confirmation, the response will include an approval request ID and a URL to an approval page for the human to approve the tool call.\nYou, as the LLM agent, should:\n\n1. Present this URL to the human as a clickable markdown link. Tell them that they have to approve this tool call at that URL, and that they should tell you when they have approved the operation.\n2. The human will approve that call.\n3. After the human tells you they have approved the operation, you must call the tool again with the `approval_token` parameter and the exact same parameters. The operation will then go through.\n"
    },
    "stripe_api_operation_id": {
      "type": "string",
      "description": "The operation ID to execute (e.g. 'PostCustomers', 'GetPaymentIntents')"
    }
  }
}

• Data resourceStripe API

  Stripe · payments

  name mention0.75

Parent server