Uwear

Improve Art Direction

iterate_art_direction

Queue feedback-driven revision of an existing ArtDirection without resending its markdown. Existing authoring references are included automatically. Use save=false for a reviewable draft, or save=true to update the same company ArtDirection with stale-edit protection. System ArtDirections support drafts only. Poll get_art_direction_authoring_job for the result.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Optional rename request
`save`	No	False returns an unsaved revision draft; true updates this same company ArtDirection
`sources`	No	Optional new supported authoring sources such as text, public URLs, or uploaded files
`feedback`	Yes	What the ArtDirection author should preserve, change, add, or remove
`image_urls`	No	Draft-only new visual sources; use persistent attachments when save=true
`art_direction_id`	Yes	Existing ArtDirection ID to revise
`reference_image_attachments`	No	New persistent authoring references to add alongside existing references

TDQS

A4.9/5.0

Behavior5/5

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

The description discloses important behavioral traits beyond the annotations: it is a queued/asynchronous operation, it preserves existing authoring references automatically, save=true includes stale-edit protection, and system ArtDirections have draft-only restrictions. This adds significant context that the annotations alone do not convey.

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 four sentences, front-loaded with the primary action, and every sentence contributes distinct value: queueing behavior, automatic references, save semantics, system restriction, and polling instruction. No wasted words or redundancy with the schema.

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?

Given the absence of an output schema, the description appropriately directs users to poll get_art_direction_authoring_job for the result, making the async flow complete. It also covers the key edge cases (system drafts only, stale-edit protection) and the distinction between draft and saved updates, making the tool's behavior clear without needing more details.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds parameter-specific meaning by clarifying the save=true/false semantics (draft vs. permanent update) and the system ArtDirection draft-only restriction. It also clarifies that existing references are included automatically, which supplements the optional nature of sources and reference_image_attachments parameters.

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 queues a feedback-driven revision of an existing ArtDirection without resending markdown, which is a specific verb+resource action. It distinguishes itself from siblings like create_art_direction and update_art_direction by emphasizing the feedback-driven iterative nature and automatic inclusion of existing references.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit usage guidance is provided: use save=false for a draft, save=true to update the same company ArtDirection with stale-edit protection, and system ArtDirections support drafts only. It also directs the user to poll get_art_direction_authoring_job for results, clarifying the expected follow-up workflow.

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

All Uwear 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

A3.5/5.0

Disambiguation3/5

Most tools target distinct resources and have detailed descriptions, but several closely related families exist: create_credit_checkout_session vs mcp_create_credit_checkout_session, the propose_brief/confirm_brief/update_brief lifecycle, and the many avatar/upload entry points. An agent must read long caveats carefully to avoid selecting the wrong tool.

Naming Consistency4/5

The vast majority of tool names follow a predictable snake_case verb_noun pattern (list_*, get_*, create_*, update_*, propose_*). The mcp_* prefix group and varied creation verbs (create/upload/save/add/generate) are minor deviations, though mcp_create_credit_checkout_session duplicating create_credit_checkout_session adds some confusion.

Tool Count1/5

With 67 tools, this is an extreme mismatch by the rubric's own 50+ threshold, far beyond the typical 3-15 well-scoped range. Many tools are narrow lifecycle steps such as two-phase local uploads, app-only montage internals, and multiple ArtDirection authoring variants, making the agent-facing surface very heavy.

Completeness3/5

The core generation, brief, montage, and QA workflows are covered thoroughly with polling and result retrieval. However, notable lifecycle gaps exist: outfits, locations, avatars, and tags mostly have create/list/get but no update or delete, and delete_template is the only delete tool in the entire set.

Resources

Need Help?