Skip to main content
Glama

Update a drop's settings

dropthis_update_settings
Idempotent

Update an existing drop's settings—title, visibility, password, noindex, expiry, metadata, and routing—using its drop ID. Content is not changed.

Instructions

Change an EXISTING drop's settings — title, visibility (public/unlisted), password, noindex, expiry, metadata, or its routing (move onto a custom domain / back to the shared pool, and rename its vanity slug) — by its drop_… id (id-only). Does not touch the content at the URL: to replace content use dropthis_update_content; to create a new drop use dropthis_publish. For a public URL or slug, call dropthis_resolve first to get the drop_… id. Idempotent — applying the same values again is a no-op.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugNoRename the drop's vanity slug — valid on path-mode custom domains only: 1-63 lowercase letters/digits/hyphens. A taken slug returns 409; setting one on the shared pool returns 422.
titleNoNew drop title.
domainNoMove the drop onto this custom domain — the hostname of a LIVE domain on this account (see dropthis_domains_list), or pass 'shared' to move it back to the shared pool. Path-mode domains serve it at https://{domain}/{slug}/; a dedicated domain serves it at the hostname root and conflicts (409) once occupied.
drop_idYesThe `drop_…` id of the drop to update (id-only — a URL or slug is rejected; call dropthis_resolve to turn a public URL/slug into its id first).
noindexNoPrevent search-engine indexing (true), allow it (false), or null to clear.
metadataNoArbitrary JSON key-value metadata.
passwordNoSet a password required to view the drop, or pass null to remove an existing one. Setting one is Pro/Business only — on Free/Keep the server returns feature_not_in_plan (403) with an upgrade_url; removing (null) is always allowed.
expires_atNoAuto-delete after this ISO 8601 timestamp (e.g. 2026-12-31T00:00:00Z), or null to clear.
visibilityNopublic (default) or unlisted. Unlisted is link-only: anyone with the URL can view the drop, but it is excluded from any public listing or discovery.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoThe drop's permanent drop_… id — persist it for every follow-up tool.
urlNoThe canonical, always-branded public URL (share with humans).
nextNoStructured follow-up hints keyed by action.
slugNoURL slug — a locator, not an id.
titleNo
rawUrlNoRaw-bytes URL for a single non-HTML file; null for HTML drops and collections.
statusNo
noindexNo
metadataNo
revisionNo
expiresAtNo
sizeBytesNoTotal published bundle size in bytes — check before iterating on a heavy page.
workspaceNoThe workspace this drop belongs to {id, slug, name, kind}.
visibilityNo
passwordProtectedNo
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, and the description reinforces this with 'Idempotent — applying the same values again is a no-op.' It adds useful behavioral context beyond the annotations: the operation 'does not touch the content at the URL' and requires a `drop_…` id, both of which help avoid misuse.

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 yet information-dense: four sentences cover purpose, scope, sibling differentiation, prerequisites, and idempotency. Every sentence earns its place and the most important information is front-loaded.

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 tool's complexity (9 parameters, nested metadata object, output schema), the description is complete: it explains what is updated, what is not touched, how to get the required id, and how it differs from related tools. The output schema exists, so return-value details are not needed in the description.

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 100%, so the baseline is 3. The description lists the fields and mentions routing (custom domain/shared pool, slug rename), but does not add substantial meaning beyond the already-detailed schema descriptions of each parameter.

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 'Change an EXISTING drop's settings' — a specific verb, resource, and scope — and enumerates exactly which settings (title, visibility, password, noindex, expiry, metadata, routing). It also distinguishes itself from siblings by explicitly naming dropthis_update_content for content replacement and dropthis_publish for creation.

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?

The description gives explicit when-to-use guidance: it is for updating settings, not content, and points to dropthis_update_content and dropthis_publish as alternatives. It also tells users to call dropthis_resolve first when they only have a public URL or slug, which is clear prerequisite context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dropthis-dev/dropthis-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server