Cannon Studio

List Cannon Studio Toolkits

list_toolkits

Read-onlyIdempotent

List first-party Cannon Studio image, video, audio, subtitle, editing, Composer, and 3D toolkit surfaces, including which ones are developer-API operations and which should be opened in the app or routed through Director Mode. Public read-only: no auth, no state changes, no charges.

Input Schema

TableJSON Schema

Name	Required	Description
`action`	No	Optional action filter such as generate, edit, upscale, trim, stitch, lip_sync, transcribe, or delivery.
`family`	No	Optional toolkit family filter such as image, video, audio, subtitles, editing, motion, composer, script, or 3d.
`media_type`	No	Optional media filter such as image, video, audio, subtitles, model3d, script, or timeline.
`project_context_only`	No	Set true to return only toolkit surfaces that can operate from selected project or Director Mode asset context.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	Yes
`toolkits`	Yes

TDQS

A4.4/5.0

Behavior5/5

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

The description goes beyond annotations by explicitly stating 'Public read-only: no auth, no state changes, no charges.' This adds valuable context about access control, side-effect freedom, and cost, which is highly relevant for agent decision-making. It aligns with the readOnlyHint and destructiveHint annotations without contradiction.

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?

The description is a single, information-dense sentence that front-loads the action and resource, lists key categories, and includes crucial safety/behavioral notes. No wasted words or redundancy.

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?

The description is largely complete for a read-only list tool with no required parameters. It explains the purpose, routing nuances, and safety profile. However, it does not explicitly compare with sibling listing tools or describe output structure, though the presence of an output schema mitigates the latter. Overall, it covers the essential context well.

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?

The input schema provides complete descriptions for all four parameters (action, family, media_type, project_context_only), and the description does not add additional parameter-level semantics. Since schema coverage is 100%, the baseline of 3 is appropriate; the description's focus is on output characteristics rather than parameter guidance.

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 clearly states the tool's function: listing specific categories of Cannon Studio toolkit surfaces (image, video, audio, etc.) and highlighting API vs. app/Director Mode routing. This specific verb+resource scope distinguishes it from sibling tools like list_capabilities and list_offerings.

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?

The description provides clear context on what information the tool returns (which toolkits are API operations vs. app/Director Mode), which signals when to use it. However, it does not explicitly mention alternatives or when not to use it, so it misses the highest bar of explicit exclusions.

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

All Cannon Studio tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation5/5

Each tool targets a distinct resource or action: status, comparison, creation, estimation, fetching, API docs, checkout, generation polling, model availability, pricing, capabilities, offerings, toolkits, workflow recommendation, and knowledge search. Even the get_* and list_* tools have clear, non-overlapping purposes.

Naming Consistency3/5

Most tools follow a verb_noun pattern (create_generation_request, list_offerings, get_checkout_link), but there are exceptions: api_status is a noun, and fetch and search are single verbs without an object. The mix of get/list/compare/recommend/search/fetch is readable but not perfectly uniform.

Tool Count5/5

15 tools is at the upper bound of the well-scoped range, but each tool serves a clear, distinct purpose in the Cannon Studio domain—from estimation and creation to knowledge retrieval and workflow recommendation. No tool feels redundant or superfluous.

Completeness3/5

The surface covers creation, estimation, polling, knowledge, and commercial operations, but the generation lifecycle is incomplete: there is no update, cancel, or list tool for generation requests, and the create tool explicitly cannot be cancelled through MCP. This is a notable gap for agents managing ongoing work.

Resources

Need Help?