Skip to main content
Glama
ghl-mcp-server-v2

ghl-mcp-server-v2

by zackscriven

ghl_marketplace_get_rebilling_config

Read-onlyIdempotent

Retrieve rebilling configuration for an app subscription and usage plans by app ID and sub-account location ID, so you can inspect the plans tied to an authenticated location.

Instructions

Get rebilling config for an app subscription and usage plans Get rebilling config for an app subscription and usage plans for the authenticated sub-account. This endpoint returns the subscription and usage plans for an app. Endpoint: GET /marketplace/app/{appId}/rebilling-config/location/{locationId} (Version header: v3; source: v3/marketplace-v3.json) Requires a Sub-Account (location) token. OAuth access token only — Private Integration Tokens are rejected. OAuth scopes: oauth.readonly

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": {
      "appId": "<appId>",
      "locationId": "<locationId>"
    },
    "name": "ghl_marketplace_get_rebilling_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesID of the app to get rebilling config
locationIdYesID of the Sub-Account location to get rebilling config for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), but the description adds genuinely non-obvious operational context: it requires a Sub-Account (location) token, only OAuth access tokens are accepted (Private Integration Tokens rejected), and it names the required OAuth scope oauth.readonly. That auth detail is exactly the kind of thing annotations do not carry.

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?

Useful content (endpoint, auth, scope) is present, but the first sentence is duplicated verbatim and the endpoint/method/version scaffolding is bulky. Front-loading is fine but roughly one full sentence is wasted on repetition.

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?

With no output schema, the description does state what the endpoint returns (the subscription and usage plans for an app), and it covers auth prerequisites and the endpoint path. For a simple two-param read tool this is close to complete; only explicit alternative routing 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% with both parameters documented, so the baseline is 3. The description only implies appId and locationId via the endpoint path template and adds the semantic note that locationId is the sub-account being queried, but supplies no format or constraint detail beyond the schema.

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?

States a specific verb and resource: 'Get rebilling config for an app subscription and usage plans'. The core purpose is clear, but the opening sentence is repeated verbatim as the second sentence, and there is no explicit differentiation from the closest sibling (ghl_saas_update_rebilling), which the agent must infer by the get/update contrast.

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

Usage Guidelines3/5

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

Usage is implied by the read-only 'get' framing and the constraint 'for the authenticated sub-account', but no explicit when-to-use vs when-not-to-use guidance or routing to alternatives is given. The sibling ghl_saas_update_rebilling for mutations is never referenced.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools