One tool per endpoint on an API this size means hundreds of definitions riding along on every turn. List, describe, invoke keeps the standing cost at three and moves the discovery into the conversation where it belongs. The trade is a round trip before the first real call, which is almost always worth it. Note the scope: admin. This is a connection that can act across your Whop business, so grant it deliberately and disconnect it when the task is done.
Whop runs commerce for creators — memberships, products, payments. Their hosted endpoint exposes an operation registry derived from their API rather than a hand-curated tool list.
The API surface itself, reached by discovery. Their published package offers either one tool per endpoint or a dynamic mode with three meta-tools: list the endpoints, get one's schema, then invoke it. A separate documentation endpoint handles search over the docs.
OAuth with dynamic client registration — the authorisation and token endpoints live on the same host, so a compliant client needs nothing pre-provisioned. The scope requested is admin. Disconnect the authorisation when you no longer need it.
Admin enables it, then paste and authorize — add the endpoint to your client, then approve the OAuth consent screen