3DLogo.io

Get a project

get_project

Read-onlyIdempotent

Details and links for one saved project by id: where it opens, its public page if published, the GLB for meshes, and with include_config the saved workspace settings (material, lighting, motion). For a picture of it, call get_project_preview.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`include_config`	No	Also return the saved workspace config (large)

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`url`	Yes	Opens the project in its studio
`kind`	Yes
`title`	Yes
`config`	No
`canEdit`	Yes
`isPublic`	Yes
`modelUrl`	Yes	Public GLB, for published meshes
`shareUrl`	Yes	Public page, when published
`inputType`	Yes
`kindLabel`	Yes
`updatedAt`	Yes	ISO 8601
`accessRole`	Yes
`hasArtwork`	Yes	False until the project has been opened and saved once in the studio
`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.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds meaningful behavioral context: it returns openings, public page only if published, the GLB, and workspace settings only when include_config is set. No contradiction with annotations.

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 tight sentences with no wasted words. The first sentence fronts the core purpose and return contents, and the second sentence immediately routes to the relevant sibling. Every phrase earns its place.

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 simple get-by-id scope, read-only annotations, and existing output schema, the description covers the essential return parts, conditional behavior, the include_config toggle, and the sibling tool for previews. Nothing an agent needs to invoke it correctly is missing.

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 50% and the schema only describes include_config as 'Also return the saved workspace config (large)'. The description enriches this by listing the config contents (material, lighting, motion) and clarifies id as the project identifier. This compensates well for the partial schema coverage.

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 opens with 'Details and links for one saved project by id,' identifying the exact verb, resource, and scope. It also distinguishes itself from get_project_preview by explicitly directing image requests elsewhere.

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?

It clearly states when to use this tool: when you need the details and links for one saved project. It names the alternative get_project_preview for a picture, and clarifies the conditional include_config behavior, making usage guidance explicit.

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?