Skip to main content
Glama

Revdoku

by com.revdoku

Bucket Set Public Slug

bucket_set_public_slug

Paid plans only: rename an existing website publication's .revdoku.site URL. If the site is live, files are republished under the new prefix; if it is unpublished, only the saved URL is changed for the next publish. Free websites retain their randomized URL. Fails with BUCKET_VISIBILITY_CHANGE_LOCKED if visibility is locked.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bucket_idYesRevdoku bucket id returned by bucket_list or bucket_get, for example bkt_...
public_slugYesThe new slug: lowercase letters, numbers, and hyphens, at least 9 characters. Avoid reserved/restricted words; if rejected as reserved, choose a different slug.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
guidanceNo
publicationYes

TDQS

A4.5/5.0
Behavior5/5

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

Description discloses republish behavior for live sites, saved URL changes for unpublished sites, and the BUCKET_VISIBILITY_CHANGE_LOCKED error – all beyond the annotations' basic flags. This gives the agent concrete expectations about side effects and failure modes.

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 sentences convey plan restriction, action, conditional behavior, and error condition with no filler. First sentence front-loads the most critical constraint.

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 2-parameter schema and output schema, the description covers essential context: eligibility, behavior in both states, and an error case. The tool is simple enough that no additional details are required.

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 descriptions already cover both parameters (bucket_id format and public_slug rules), so the description adds no extra parameter info. With 100% schema coverage, no compensation is needed.

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?

Description states 'rename an existing website publication's <slug>.revdoku.site URL' – a specific verb and resource, clearly distinguishing from sibling tools like bucket_publish or bucket_update. The paid-only prerequisite is also front-loaded.

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?

Mentions 'Paid plans only' and 'Free websites retain their randomized URL', providing an explicit condition for use. However, it doesn't name alternative tools or explicitly say when not to use other bucket_* tools, so it falls short of full alternative guidance.

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

All Revdoku toolsInspect
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.6/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, but a few overlaps exist: bucket_file_move and bucket_file_rename both handle same-bucket renames/moves, and bucket_file_reorganize overlaps with copy/move operations. The detailed descriptions help clarify, but the boundaries aren't always obvious.

Naming Consistency4/5

The naming follows predictable patterns: bucket_<verb> for bucket-level actions, bucket_file_<verb> for file operations, bucket_publication_<verb> for publications, and website_preview_* for previews. Minor deviations like bucket_create_from_template, bucket_set_public_slug, and bucket_update_publication_access deviate slightly but remain readable.

Tool Count2/5

At 42 tools, the server is overweight for its scope. While the platform is feature-rich, many tools are narrowly specialized (e.g., bucket_publication_leads, bucket_lock_visibility_changes) and some are redundant (file_move vs file_rename vs file_reorganize), making the surface larger than necessary for an MCP server.

Completeness3/5

The tool set covers the full bucket lifecycle and most file operations, but there is no direct file delete tool (only via delete_missing in write_many or cross-bucket move soft-delete) and binary uploads are explicitly delegated to the CLI/REST. These are notable gaps for a complete file management workflow.

Resources