verse-mcp

Revoke a private share link

revoke_share_link

DestructiveIdempotent

Revoke a private share token so its link stops working. Pass the shareId from create_share_link, or omit it to list active share ids.

Instructions

Revoke one private share token so its link stops working. Use the shareId returned by create_share_link, or call with only scene to list the active share ids. Needs an account token.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "scene": "<scene>"
    },
    "name": "revoke_share_link"
  }
}

Input Schema

Name	Required	Description	Default
`scene`	Yes	Scene id (e.g. palm-villa-0a1b2c3d4e5f), the job id returned by upload_scene, or a Verse share link.
`share_id`	No	The shareId to revoke. Omit to list active ones.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 15, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Adds context the annotations do not carry: the auth requirement ('Needs an account token') and the user-visible effect of the destructive write (link stops working). It also reveals a surprising secondary behavior — calling with only `scene` performs a read/list rather than a revoke — which matters given destructiveHint=true. It does not say whether revocation is reversible or what a successful revoke returns.

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?

Three short sentences, front-loaded with the effect, then the id source, then the fallback mode and auth need. No filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description does not describe the return shape of either mode (e.g. what the listing returns or what a revoke response confirms), which leaves a small gap. For a two-parameter destructive tool with rich annotations, the purpose, auth requirement, and dual-mode behavior are otherwise covered.

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 coverage is 100%, so both parameters are already documented, giving a baseline of 3. The description adds useful provenance for `share_id` (comes from create_share_link) and the omit-to-list semantics, but the naming drifts from the schema's `share_id` to camelCase `shareId`, and it adds nothing about the accepted scene-id/share-link forms already in the schema.

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?

States a specific verb (revoke) and resource (private share token) plus the observable consequence ('so its link stops working'). An agent can distinguish this from create_share_link and the listing siblings without opening any schema.

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?

Explicitly tells the agent where to get the id ('the `shareId` returned by create_share_link') and describes the alternate list-only invocation with `scene` alone. It stops short of stating when not to revoke (e.g. ownership/permission prerequisites beyond the account token).

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

Deploy Server