Skip to main content
Glama

Get billing URL

campaignstack_get_billing_url
Read-onlyIdempotent

Use this when the user wants to upgrade or downgrade their workspace subscription. Returns the workspace billing settings URL, where the signed-in human reviews and confirms the change. This read-only tool does not change billing or make a charge. Instead use campaignstack_get_workspaces for subscription state and balances.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "campaignstack_get_billing_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceIdNoWorkspace ID. Omit it when this connection reaches one workspace: a workspace key (cs_) is bound to its own, and a user key (csu_) or connected app whose person belongs to exactly one workspace defaults to that one. Required only when the person belongs to several; the error then lists them, and campaignstack_whoami reports them too.

Output Schema

NameRequiredDescriptionDefault
urlNo
workspaceIdNo
requiresHumanConfirmationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the description's added claim that it 'does not change billing or make a charge' reinforces rather than repeats. It goes beyond the annotations by explaining the human-in-the-loop handoff: a signed-in human reviews and confirms the change at the returned URL. It does not address authorization requirements or what the URL response looks like beyond the link, keeping it just short of a 5.

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

Conciseness5/5

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

Four short sentences, front-loaded with the trigger condition, then the return value, then the safety clarification, then the alternative. Every sentence carries distinct information and none repeat structured fields verbatim.

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 single-optional-parameter read tool with full schema coverage, an output schema, and complete annotations, the description covers intent, return value, safety profile, and the correct alternative. Nothing an agent needs to select or call it correctly is missing.

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 100% and the workspaceId description already spells out the omission rules for cs_ and csu_ keys and the multi-workspace error case. The tool description adds no parameter-level meaning, so the baseline 3 applies when the schema does all the work.

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?

The description uses a specific verb and resource ('Returns the workspace billing settings URL') and immediately scopes it to subscription upgrade/downgrade intent. An agent can distinguish it from campaignstack_get_workspaces, which is explicitly named as the tool for reading subscription state.

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?

It states exactly when to use it ('user wants to upgrade or downgrade their workspace subscription') and explicitly redirects to campaignstack_get_workspaces for subscription state and balances. The when-not condition is named alongside the alternative, leaving nothing to inference.

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