list_my_foldersList the folders in your Switch library (id, name, parent). Use this to find an existing folder before move_asset or create_folder.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds useful context by specifying the returned fields and the library scope, but does not mention potential pagination or hierarchy depth. Overall, it adds meaningful behavioral detail beyond the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences long, front-loaded with the core purpose, and every clause adds value. The first sentence states what it does, and the second explains when to use it, with no redundant or filler content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple, parameter-less listing tool with good annotations, the description is complete. It states the resource, the information returned, and the recommended usage context. No output schema is needed because the description already lists the output fields.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the baseline is 4. The description correctly implies that no input is needed, and the empty schema confirms this. Any attempt to explain parameters would be superfluous.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool 'List the folders in your Switch library' with a specific verb and resource, and even details the returned fields (id, name, parent). It is well distinguished from sibling list tools like list_my_assets and list_my_videos by explicitly naming 'folders'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states when to use the tool: 'Use this to find an existing folder before move_asset or create_folder.' This provides direct guidance on the appropriate context and links to related operations, making the usage intent unambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Several tools occupy nearly identical semantic ground: apply_iphone_realism and apply_ugc both describe casual phone-shot looks, upload_media and upload_reference_asset both accept uploads, and analyze_video overlaps heavily with analyze_video_report. The many apply_* style tools are essentially one tool parameterized by style, so agents can easily select the wrong one.
Most tools follow a clear verb_noun snake_case pattern such as generate_image, list_my_videos, get_editor_run, and upscale_video. A few outliers like voice, talking_avatar_video, and video_to_prompt do not use the same verb-first convention, but they are still readable and do not create significant confusion.
At 55 tools, the surface is far beyond what is appropriate for an MCP server; many of these be collapsed or parameterized, especially the 10 apply_* style wrappers and several overlapping upload/status helpers. Even for a broad media platform, this scale forces a huge context window and makes selecting the right tool impractical.
The surface covers generation, media display, video analysis, and Editor workflows well, but there are obvious gaps in library lifecycle management: move_asset and create_folder are referenced in tool descriptions without being exposed, and there is no clean way to delete or reorganize media assets. Agents following the descriptions will try to call tools that do not exist.