Skip to main content
Glama

Valet

by io.github.valetdotdev

Delete a website

delete_site
DestructiveIdempotent

Permanently delete a website and stop serving it. Identify it by name, which requires connecting a Valet account, or by the site_token returned when it was published anonymously — whoever published a site can always take it down. This cannot be undone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoGive this or site_token. The site's name, which requires a connected Valet account.
org_nameNoThe Valet organization the site belongs to. Omit to use the organization the account joined first.
site_tokenNoGive this or name. The token returned when the site was published anonymously; it identifies that one site.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"The site's name. Requires a connected Valet account."New value: +"Give this or site_token. The site's name, which requires a connected Valet account."
    • changedInput schema / properties / site_token / description
      Previous value: -"The token returned when the site was published anonymously. It identifies that one site."New value: +"Give this or name. The token returned when the site was published anonymously; it identifies that one site."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already mark destructiveHint:true and idempotentHint:true; the description adds crucial context: 'Permanently delete', 'cannot be undone', and the identification logic. No contradiction.

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 concise sentences. The first sentence front-loads the core purpose and effect. Every word is necessary; no redundancy.

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 simple delete tool with strong annotations and no output schema, the description fully covers all essential aspects: action, effect, identification methods, persistence, and scope. No gaps remain.

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

Parameters5/5

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

Schema coverage is 100% with descriptions. The tool description adds value by explaining the semantics of name vs. site_token (account requirement vs. anonymous token) and org_name optionality. This goes beyond what the schema alone provides.

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 ('delete') and resource ('website'), clearly distinguishing it from siblings like rename_site or publish_site. It covers the key aspects: permanent removal and stopping serving.

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 explains two identification methods (name with Valet account vs. site_token from anonymous publish) and who can delete. It implicitly tells when to use this tool (to delete) but does not explicitly contrast with alternatives like updating or deprecating. Still very clear for a delete operation.

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

All Valet 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

A4.4/5.0
Disambiguation5/5

Every tool targets a distinct resource and action. The three list_* connector tools are clearly separated by scope (catalog vs attachable vs attached), and the site management tools are unambiguous.

Naming Consistency5/5

All tool names follow a uniform verb_noun snake_case pattern. Each name directly states the action and object, with no mixed conventions or vague verbs.

Tool Count4/5

16 tools is slightly above the typical well-scoped range, but the set covers two clear domains—site publishing and connector management—and each tool has a distinct role. The count is justified, if a bit heavy.

Completeness4/5

Site lifecycle is well covered: publish, list, get, rename, delete, access, and share. The connector lifecycle covers create, attach, detach, and call, but lacks delete/update connector operations, which are a minor gap.

Resources