Skip to main content
Glama

Manage the membership

manage_membership
Destructive

Start a plan, open the payment details page, answer the questions about a cancellation the member made, and buy a custom domain or extra campaigns. Prices come from get_account membership or get_outreach campaigns (packs), and pricingAcceptance is the exact value the member accepted. Payment happens on a page the member opens. Cancelling is never done through an agent: the member cancels the membership in Settings › Membership, or ends a free trial on Membership, on applystead.com. Actions: start_checkout, billing_portal, cancellation_feedback, buy_domain, buy_extra_campaigns. Call with action "help" for each action's fields.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "manage_membership"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
paramsNoFields for the action. Call with action "help" to list each action's fields.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "start_checkout",
      -  "billing_portal",
      -  "cancellation_feedback",
      -  "buy_domain",
      -  "buy_api_credits",
      -  "buy_extra_campaigns",
      -  "help"
      -]New value: +[
      +  "start_checkout",
      +  "billing_portal",
      +  "cancellation_feedback",
      +  "buy_domain",
      +  "buy_extra_campaigns",
      +  "help"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "start_checkout",
      -  "billing_portal",
      -  "cancel_upgrade_trial",
      -  "cancel",
      -  "cancellation_feedback",
      -  "buy_domain",
      -  "buy_api_credits",
      -  "buy_extra_campaigns",
      -  "help"
      -]New value: +[
      +  "start_checkout",
      +  "billing_portal",
      +  "cancellation_feedback",
      +  "buy_domain",
      +  "buy_api_credits",
      +  "buy_extra_campaigns",
      +  "help"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "start_checkout",
      -  "billing_portal",
      -  "cancel_upgrade_trial",
      -  "cancel",
      -  "cancellation_feedback",
      -  "buy_domain",
      -  "buy_api_credits",
      -  "help"
      -]New value: +[
      +  "start_checkout",
      +  "billing_portal",
      +  "cancel_upgrade_trial",
      +  "cancel",
      +  "cancellation_feedback",
      +  "buy_domain",
      +  "buy_api_credits",
      +  "buy_extra_campaigns",
      +  "help"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "start_checkout",
      -  "billing_portal",
      -  "preview_upgrade",
      -  "upgrade",
      -  "start_upgrade_trial",
      -  "cancel_upgrade_trial",
      -  "preview_term",
      -  "change_term",
      -  "preview_plan_change",
      -  "change_plan",
      -  "switch_trial_plan",
      -  "cancellation_questions",
      -  "cancel",
      -  "cancellation_feedback",
      -  "buy_domain",
      -  "buy_api_credits",
      -  "help"
      -]New value: +[
      +  "start_checkout",
      +  "billing_portal",
      +  "cancel_upgrade_trial",
      +  "cancel",
      +  "cancellation_feedback",
      +  "buy_domain",
      +  "buy_api_credits",
      +  "help"
      +]
  5. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true; the description adds the crucial context that payment happens on a page the member opens, so the agent is not itself processing payment. It also bounds the destructive surface by declaring cancellation is out of scope entirely. It does not say whether a started checkout is reversible or what state each action leaves behind, so it is not exhaustive.

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

Conciseness3/5

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

The opening sentence is a run-on that blends five distinct actions and is imprecise about which action each clause maps to. The trailing action list then repeats the enum already present in the schema, though it does aid scanning. Content is front-loaded and not padded, but the structure could be tightened.

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

Completeness4/5

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

For a five-action tool with a free-form params object and no output schema, the description covers the essentials: what each action does at a high level, where prices come from, that payment is external, that cancellation is excluded, and how to discover per-action fields via "help". What remains missing is any indication of what each action returns or how the member is handed off to the payment page.

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

Parameters3/5

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

Schema coverage is 50% and the params object is free-form with additionalProperties, so the description has to carry weight; it does add real meaning by defining pricingAcceptance as the exact value the member accepted and by pointing to action "help" for per-action field discovery. That is useful but still defers the actual field list to a runtime call rather than documenting it, so it lands at baseline-plus rather than high.

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

Purpose4/5

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

The description names concrete operations (start a plan, open the payment details page, submit cancellation feedback, buy a domain or campaign packs) and then enumerates the exact action values, so an agent can map intent to action. It is a bundled multi-action tool rather than a single verb+resource, and the prose-to-action mapping is loose in places ("answer the questions about a cancellation" = cancellation_feedback), which keeps it short of a 5.

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

Usage Guidelines4/5

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

It explicitly excludes one path: cancelling is never done through an agent and is routed to Settings › Membership or the free-trial flow on applystead.com. It also states where prices must be sourced (get_account membership or get_outreach campaigns) before calling. It does not contrast start_checkout vs billing_portal or say when each purchase action is appropriate, so it is clear context without full when/when-not coverage.

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.