Clip Studio MCP

get_account

Read-only

Plan and usage for the signed-in Clip Studio account. resetsAt is an ISO timestamp when the monthly allowance resets, or null when there is no reset window. Includes offerCheckout price IDs for Clip Pro $19/mo and Studio Elite $39/mo after a 402.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`email`	No	Account email, or null when unknown.
`userId`	No	Signed-in Clip Studio user id.
`credits`	No	Remaining generation allowance in internal usage units.
`resetsAt`	No	ISO timestamp when the monthly allowance resets, or null when there is no reset window (no period, unlimited operator, or unknown).
`planUsage`	No	Allowance already used this cycle (internal units).
`packBalance`	No	Add-on pack balance (internal units).
`offerCheckout`	No	Clip Pro $19 and Studio Elite $39 Stripe price ids for create_checkout_url after a 402.
`planAllowance`	No	This month’s plan generation allowance (internal units).
`planRemaining`	No	Plan allowance still unused this cycle (internal units).

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 8, 2026

changedOutput schema / properties / email / description

Previous value: -"Account email, when known."New value: +"Account email, or null when unknown."

changedOutput schema / properties / email / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / resetsAt / description

Previous value: -"ISO timestamp when the monthly allowance resets, when known."New value: +"ISO timestamp when the monthly allowance resets, or null when there is no reset window (no period, unlimited operator, or unknown)."

changedOutput schema / properties / resetsAt / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

First observedSep 20, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish the read-only, non-destructive, closed-world profile, so the description adds value beyond them by explaining field semantics: resetsAt is an ISO timestamp that is null when there is no reset window, and checkout price IDs appear in the 402 path. That is meaningful behavioral context, though return handling is not fully described.

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?

Three tight sentences with the purpose front-loaded, then field semantics. No filler, though most of the length is devoted to describing output fields that a dedicated output schema may already cover.

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 zero-parameter read tool with annotations and an existing output schema, the description covers what it is and why the notable fields behave as they do. Auth is only implied by 'signed-in', and no error/pagination behavior is mentioned, leaving a small gap.

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?

The tool takes zero parameters, so the baseline is 4. There is nothing for the description to disambiguate, and it correctly does not invent parameter guidance.

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 the resource precisely — the plan and usage for the signed-in Clip Studio account — which is a noun-phrase but unambiguous about what is retrieved. It does not name or contrast against any sibling tool, so it falls short of the differentiation a 5 requires.

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?

There is no explicit when-to-use statement or named alternative, but the sentence about offerCheckout price IDs being included 'after a 402' implies the scenario in which the returned data matters. Usage is inferred rather than stated.

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

All Clip Studio MCP 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?