Mark

Get Plan Usage

get_plan_usage

Read-onlyIdempotent

Shows this workspace's Mark plan (none, starter, growth, enterprise), subscription status, billing interval, trial end and current period end, and the 4 plan caps with used and limit: sites, trackedKeywords, aiPrompts (active buyer questions times configured active markets) and socialAccounts. limit is null when nothing limits that cap. These are the numbers Settings > Billing shows; the card on file shows only there. Starting a trial, paying, upgrading or changing the card happens only in the Mark app: billingUrl opens Settings > Billing, and upgradeUrl is set when a bigger plan is available. Does not change anything. Related: get_workspace.

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": "get_plan_usage"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`caps`	Yes
`plan`	Yes
`status`	Yes
`billingUrl`	Yes
`upgradeUrl`	Yes
`trialEndsAt`	Yes
`billingInterval`	Yes
`currentPeriodEnd`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 21, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare read-only/idempotent/non-destructive, and the description adds meaningful context beyond them: 'Does not change anything,' the null-limit semantics ('limit is null when nothing limits that cap'), and the explicit routing of all write/billing actions to the external app. This gives an agent complete behavioral confidence.

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

Conciseness4/5

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

Front-loaded with what is shown, then behaviors, then the no-mutation/where-to-mutate note. Every sentence carries information, though it is slightly dense; no wasted filler.

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?

An output schema exists, so return format needn't be re-explained, and the description still fully covers cap semantics, null-limit behavior, non-mutation, and where billing changes occur. Nothing needed to select or interpret the tool is missing.

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

Parameters4/5

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

Zero parameters, so baseline is 4 per the rubric. The description does add output semantics (aiPrompts = active buyer questions × configured active markets, null limit meaning), which is extra useful context even though the schema carries no parameters to document.

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?

States a specific verb and resource ('Shows this workspace's Mark plan') and enumerates exactly what is returned: plan tier with enum values, subscription status, billing interval, trial/period end, and the 4 caps with used/limit. It is clearly distinguishable from generic workspace tools like get_workspace.

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?

Explicitly scopes usage: these are Settings > Billing numbers, card-on-file is only there, and all mutations (trial, pay, upgrade, card change) happen in the Mark app via billingUrl/upgradeUrl. It names the related get_workspace but stops short of stating the exact split of when to pick one over the other.

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

All Mark tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?