Skip to main content
Glama

Clip Studio MCP

by ai.clipstudio
OverviewDiscussionsAdmin

quote_audio_lab

Read-only

Quote an Audio Lab script. Does not generate or charge.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
voiceNoClip Studio voice name from list_audio_lab_voices (for example Russ). Not the ElevenLabs voice_id. Defaults to the product default voice.
scriptYesNarration script to quote. 5,000 characters or fewer. Character count drives the quote.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
voiceNoClip Studio voice name this quote locked in.
quoteIdYesQuote id. Pass this to the matching generate tool. Quotes expire.
expiresAtNoISO timestamp when this quote expires.
characterCountNoScript character count used for the quote.
requiredCreditsNoUsage this quote would consume from this month’s generation allowance (internal units).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / script / description
      Previous value: -"Narration script to quote. Character count drives the quote."New value: +"Narration script to quote. 5,000 characters or fewer. Character count drives the quote."
    • addedInput schema / properties / script / maxLength
      Added value: +5000
    • addedInput schema / properties / script / minLength
      Added value: +1
    • changedInput schema / properties / voice / description
      Previous value: -"Voice id from list_audio_lab_voices. Defaults to the product default voice."New value: +"Clip Studio voice name from list_audio_lab_voices (for example Russ). Not the ElevenLabs voice_id. Defaults to the product default voice."
    • changedOutput schema / properties / voice / description
      Previous value: -"Voice id this quote locked in."New value: +"Clip Studio voice name this quote locked in."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false. The description adds a billing guarantee ('does not charge') that annotations do not cover, which is genuinely valuable for an agent deciding whether it is safe to call this before committing to a generation.

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?

Two short sentences, fully front-loaded, with zero wasted words. The cost/scope constraint is stated immediately after the purpose.

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?

An output schema exists, so return values need not be described, and the two parameters are fully documented in the schema. Combined with clear read-only and no-charge framing, the definition is sufficient for correct invocation, though it could note whether the quote expires or how the price is returned.

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 description coverage is 100%, so the voice and script parameters (including the 5,000-char limit and the list_audio_lab_voices reference) are already fully documented in the schema. The description adds no parameter detail beyond that baseline.

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 (quote) and resource (Audio Lab script), and the negative clause 'Does not generate or charge' separates it from the sibling generate_audio_lab. It does not explicitly name that sibling, so it falls just short of 5.

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?

'Does not generate or charge' implies this is the pre-generation pricing step, which is useful context, but no explicit when-to-use or alternative-naming guidance is given. 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 toolsInspect
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