3DLogo.io

Duplicate a project

duplicate_project

Use when the user wants a variant without touching the original ("a gold version of this one"): copies a saved logo or coin project with its artwork, optionally under a new title; restyle the copy with update_project_style. Counts against the project cap. Does not spend credits.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`title`	No

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`url`	Yes	Opens the project in its studio
`kind`	Yes
`title`	Yes
`isPublic`	Yes
`modelUrl`	Yes	Public GLB, for published meshes
`shareUrl`	Yes	Public page, when published
`inputType`	Yes
`kindLabel`	Yes
`updatedAt`	Yes	ISO 8601
`thumbnailUrl`	Yes	Saved thumbnail; needs the owner's browser session

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed6 schema fields changedSep 6, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedOutput schema / properties / inputType / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / inputType / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / updatedAt / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / updatedAt / type
```
Added value: +[
+  "string",
+  "null"
+]
```

First observedSep 6, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations, the description discloses important behavior: the original is untouched, the copy counts against the project cap, and no credits are spent. It also clarifies that artwork is carried over, which helps the agent set user expectations accurately.

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 compact, front-loads the use case, and every sentence adds meaningful guidance: behavior, side effects, and follow-up action. No filler or redundant restating of the tool name.

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 output schema and annotations, the description covers the essential non-obvious context: source preservation, project cap effect, credit usage, and the relationship to update_project_style. It is fully adequate for an agent to select and invoke the tool correctly.

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 0%, so the description must supply meaning for the parameters. It does for 'title' ('optionally under a new title') and implies 'id' identifies the saved project, but it never explicitly names the 'id' parameter or states that it must reference an existing project, leaving partial ambiguity.

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 duplicates a saved logo or coin project along with its artwork, optionally under a new title. It also explicitly contrasts the result with update_project_style, making the core purpose unambiguous and distinguishable from sibling creation/editing tools.

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 opens with a concrete when-to-use scenario ('a gold version of this one') and explains the key consequence of not touching the original. It points to update_project_style for restyling the copy, though it does not explicitly enumerate cases where a different tool, such as create_*_logo_project, should be used instead.

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

All 3DLogo.io 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.8/5.0

Disambiguation3/5

Most tools target distinct resources, but several overlapping pairs exist: search/list_projects both find projects by title, fetch/get_project both return project details, and upload_logo_image/request_logo_image_upload are two upload paths. The descriptions help clarify boundaries, but an agent could still misselect.

Naming Consistency4/5

Tool names overwhelmingly follow a clear verb_noun snake_case pattern (create_, list_, get_, update_, delete_). Minor deviations like bare 'fetch' and 'search', plus the mixed '3d' in generate_3d_model vs '3D' in descriptions, keep it from being perfectly consistent.

Tool Count2/5

At 31 tools, this exceeds the 25+ threshold where agent tool selection becomes cognitively heavy. While the server covers a broad platform, several tools are near-redundant and could be consolidated, making the count feel inflated.

Completeness4/5

The surface covers project lifecycle, sharing/publishing, AI generation, uploads, materials, and account/plan management quite thoroughly. Minor gaps exist, such as no direct create_coin_project tool and no deletion for generation runs, but these are workable.

Resources

Need Help?