3DLogo.io

Turn off a share link

revoke_share_link

DestructiveIdempotent

Turns a share link off by token: the page, the embed and the poster stop serving within minutes. Cannot be undone; create_share_link makes a fresh one. Owner only.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`token`	Yes

Output Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	The share page
`kind`	Yes
`title`	Yes
`token`	Yes
`status`	Yes
`embedUrl`	Yes	The iframe source
`modelUrl`	Yes	The GLB, for shares of generated meshes
`videoUrl`	Yes	Turntable MP4, when one has been rendered
`createdAt`	Yes
`embedHtml`	Yes	Copy-paste iframe snippet with attribution
`expiresAt`	Yes
`oembedUrl`	Yes	oEmbed endpoint for this share
`posterUrl`	Yes	Rendered still of the design, when one exists
`projectId`	Yes
`viewCount`	Yes
`visibility`	Yes
`embedEnabled`	Yes
`allowDownload`	Yes

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 / expiresAt / anyOf

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

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

addedOutput schema / properties / modelUrl

Added value: +{
+  "anyOf": [
+    {
+      "format": "uri",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The GLB, for shares of generated meshes"
+}

changedOutput schema / required

Previous value: -[
-  "token",
-  "url",
-  "embedUrl",
-  "posterUrl",
-  "videoUrl",
-  "oembedUrl",
-  "embedHtml",
-  "kind",
-  "title",
-  "visibility",
-  "status",
-  "expiresAt",
-  "allowDownload",
-  "embedEnabled",
-  "viewCount",
-  "projectId",
-  "createdAt"
-]New value: +[
+  "token",
+  "url",
+  "embedUrl",
+  "posterUrl",
+  "videoUrl",
+  "modelUrl",
+  "oembedUrl",
+  "embedHtml",
+  "kind",
+  "title",
+  "visibility",
+  "status",
+  "expiresAt",
+  "allowDownload",
+  "embedEnabled",
+  "viewCount",
+  "projectId",
+  "createdAt"
+]

First observedSep 6, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the destructiveHint annotation, the description discloses concrete behavioral details: the page, embed, and poster stop serving within minutes, the operation cannot be undone, and only the owner may perform it. This adds meaningful context about irreversible side effects and authorization without contradicting any annotation.

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 two compact sentences that front-load the primary action and effect. Every clause adds a distinct fact: what stops serving, the time frame, irreversibility, the recovery path via create_share_link, and the owner-only restriction. There is no filler.

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?

For a single-parameter tool with an output schema and annotations that already cover readiness and destructiveness, the description covers the essential behavior, irreversibility, and authorization. The only minor omission is explicitly telling the agent where to find a token, but this is inferable from sibling tools and not necessary for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage and the only parameter, token, is explained only as 'by token' in the description, which largely repeats the property name. The description does not clarify how to obtain a token, whether it is the same token returned by create_share_link, or how a token relates to list_share_links, so it fails to compensate for the schema's silence.

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 uses a specific verb ('Turns a share link off') and names the exact resource and scope, including what stops serving: 'the page, the embed and the poster.' It also distinguishes itself from create_share_link by noting the action cannot be undone, so an agent can correctly separate it from nearby sibling 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 gives clear context for use: it is a permanent, owner-only revocation. It explicitly points to create_share_link as the alternative for obtaining a fresh link, which helps an agent decide between the two. It does not explicitly mention listing share links to discover a token, but the core when-to-use guidance is present.

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?