# RevCent MCP Guide: `GetSubscriptionRenewal`

Brief AI/MCP-focused guide for retrieving one RevCent Subscription Renewal.

---

## Operation Summary

Operation:

```text
GetSubscriptionRenewal
```

Purpose:

```text
Retrieve the details of a specific Subscription Renewal.
```

A Subscription Renewal is a specific renewal event or renewal attempt generated from a Subscription.

Simple model:

```text
Subscription = customer's recurring billing relationship
Subscription Profile = renewal schedule/rules
Subscription Renewal = one renewal event or attempt
```

Use `GetSubscriptionRenewal` when the exact 20-character Subscription Renewal ID is known and the user needs to inspect one renewal record.

---

## Related Links

| Guide | Link |
|---|---|
| Subscription Renewals Overview | `https://revcent.com/documentation/markdown/mcp/operation/OverviewSubscriptionRenewal.md` |
| Subscription Overview | `https://revcent.com/documentation/markdown/mcp/operation/OverviewSubscription.md` |
| GetSubscriptionRenewals | `https://revcent.com/documentation/markdown/mcp/operation/GetSubscriptionRenewals.md` |
| GetSubscription | `https://revcent.com/documentation/markdown/mcp/operation/GetSubscription.md` |
| RefundSubscriptionRenewal | `https://revcent.com/documentation/markdown/mcp/operation/RefundSubscriptionRenewal.md` |
| RenewSubscription | `https://revcent.com/documentation/markdown/mcp/operation/RenewSubscription.md` |
| Salvage Transaction Overview | `https://revcent.com/documentation/markdown/mcp/operation/OverviewSalvageTransaction.md` |
| BigQueryRunQuery | `https://revcent.com/documentation/markdown/mcp/operation/BigQueryRunQuery.md` |

---

## When to Use

Use `GetSubscriptionRenewal` for one known Subscription Renewal.

Good uses:

- review one renewal event,
- inspect whether a renewal succeeded, failed, or is overdue,
- review renewal amount fields,
- review customer context,
- inspect payment type,
- inspect related Transaction, PayPal Transaction, Offline Payment, Tax, Shipping, Discount, Salvage Transaction, Pending Refund, Chargeback, or Fraud Detection IDs,
- verify context before `RefundSubscriptionRenewal`,
- investigate a failed renewal before recovery,
- inspect a renewal before a support, AI Assistant, or AI Voice Agent workflow acts on it.

---

## Input Schema

Required:

| Field | Type | Description |
|---|---:|---|
| `subscription_renewal_id` | string | 20-character Subscription Renewal ID. |

Example:

```json
{
  "subscription_renewal_id": "RRRRRRRRRRRRRRRRRRRR"
}
```

---

## Useful Output Areas

`GetSubscriptionRenewal` can return detailed renewal context, including:

| Area | Examples |
|---|---|
| Amounts | `amount`, `amount_original_total`, `amount_total`, `amount_gross`, `amount_net`, `amount_fees`, `amount_captured`, `amount_settled`, `amount_remaining`, `amount_refunded`. |
| Customer | Customer ID, name, email, phone, address, enabled/blocked state, metadata. |
| Subscription context | Parent Subscription, Subscription Profile, renewal schedule/date context, overdue state where applicable. |
| Product context | Product ID/name, quantity, SKU/internal ID, subscription/trial product flags where applicable. |
| Commerce context | Campaign, currency, payment type, third-party shop. |
| Related records | Sales, Product Sales, Shipping, Tax, Discounts, Trials, Subscriptions, Subscription Renewals, Invoices, Transactions, PayPal Transactions, Offline Payments, Salvage Transactions, Pending Refunds, Chargebacks, Fraud Detections, AI Threads, AI Assistants, API Calls. |

Use related record IDs to retrieve the full lifecycle when needed.

---

## Customer-Facing AI Verification Warning

This operation may expose sensitive customer, subscription, payment, renewal, shipment, tax, refund, salvage, or lifecycle context.

If this operation is used inside a customer-facing AI flow, such as:

- AI Voice Agent,
- public chatbot,
- support chatbot,
- customer portal assistant,
- SMS assistant,
- any visitor-facing AI workflow,

the AI/MCP client should verify the visitor is actually related to the Subscription Renewal before providing details or taking action.

Recommended rule:

```text
Do not provide Subscription Renewal details to a public-facing visitor based only on the Subscription Renewal ID or a value the visitor supplied.
```

Use a secondary value from the retrieved Subscription Renewal response to verify identity.

Recommended verification examples:

| Visitor-Provided Input | Secondary Verification Value |
|---|---|
| Subscription Renewal ID | Customer email from `GetSubscriptionRenewal.customer.email`. |
| Subscription ID | Customer email or phone from the retrieved Subscription Renewal. |
| Customer name | Customer email or phone from the retrieved Subscription Renewal. |
| Phone number | Customer email from the retrieved Subscription Renewal. |
| Order/shop context | Customer email from the retrieved Subscription Renewal or related Subscription/Sale. |
| Metadata/external ID | Customer email or phone from the retrieved Subscription Renewal. |

Example safe flow:

```text
Visitor provides renewal/search input
    ↓
AI uses GetSubscriptionRenewal or a narrow operational lookup
    ↓
AI retrieves the Subscription Renewal
    ↓
AI asks the visitor to verify a secondary value from the retrieved record, such as customer email
    ↓
Only after verification:
        provide limited appropriate details
        or take an allowed action
```

Important:

```text
The secondary verification value should come from the retrieved RevCent record, not only from the visitor's original search or lookup input.
```

For example, if the visitor provides a Subscription Renewal ID, verify against the customer email returned by `GetSubscriptionRenewal` before discussing the renewal.

Do not disclose sensitive details such as:

- payment details,
- subscription details unrelated to the verified visitor,
- shipment details,
- tax details,
- fraud/risk logic,
- unrelated customer records,
- internal notes not meant for customers,
- other related records unless the visitor is verified and authorized.

For consequential actions, such as `RefundSubscriptionRenewal`, subscription cancellation/suspension, manual renewal, or salvage processing, require explicit confirmation and follow the relevant operation-specific safety guidance.


---

## Critical Reporting Rule

This Subscription Renewal lookup operation is **not** a reporting tool.

Do not use this operation for:

- counting,
- aggregations,
- metrics,
- reporting,
- data mining,
- bulk retrieval,
- broad analysis,
- document property searches,
- renewal revenue reports,
- renewal success/failure reports,
- renewal recovery reports,
- salvage recovery reports,
- renewal refund reports,
- campaign/shop/product/subscription performance metrics.

Use:

```text
BigQueryRunQuery
```

for those purposes.

Important AI/MCP behavior:

```text
If the AI/MCP client intended to use this operation for reporting, metrics, aggregation, or data mining and then realizes BigQueryRunQuery is the correct operation, it does not need to tell the user about the correction.

It should simply use BigQueryRunQuery instead.
```

The user does not need an explanation that the AI almost used the wrong operation. The correct behavior is to quietly choose the correct operation.


---

## Correct Use vs Incorrect Use

| User Intent | Correct Action |
|---|---|
| “Show me this Subscription Renewal ID.” | Use `GetSubscriptionRenewal`. |
| “Why did this specific renewal fail?” | Use `GetSubscriptionRenewal`, then related payment/salvage records. |
| “Can I refund this renewal?” | Use `GetSubscriptionRenewal` first, then confirm and use `RefundSubscriptionRenewal` if appropriate. |
| “What was renewal revenue last month?” | Use `BigQueryRunQuery`, not `GetSubscriptionRenewal`. |
| “Show failed renewals by campaign.” | Use `BigQueryRunQuery`, not `GetSubscriptionRenewal`. |

---

## Best Practices

1. Use this only for one known Subscription Renewal ID.
2. Use `GetSubscriptionRenewals` only for bounded operational lookup when the ID is unknown.
3. Retrieve before `RefundSubscriptionRenewal`.
4. Inspect related Subscription and payment records for failed-renewal support.
5. Inspect salvage transactions before recovery attempts.
6. Verify customer identity before sharing Subscription Renewal details in customer-facing AI flows.
7. Use `BigQueryRunQuery` for all reporting and analytics.

---

## Final AI/MCP Instruction

Use `GetSubscriptionRenewal` to retrieve one specific Subscription Renewal by ID.

In customer-facing AI flows, verify the visitor is related to the Subscription Renewal using a secondary value from the retrieved record, such as `customer.email`, before providing details or taking action.

Do not use this operation for reporting, metrics, counting, aggregation, data mining, or broad analysis. If the task is reporting-related, silently use `BigQueryRunQuery` instead.


---
Document Parent Directory
* [Operations](https://revcent.com/documentation/markdown/mcp/operation/index.md) - AI/MCP details and overviews for operations available within the RevCent MCP.