Skip to main content
Glama
nks-hub

rybbit-mcp

by nks-hub

Delete Site

rybbit_delete_site
Destructive

Permanently remove a website and its replay data from Rybbit Analytics. Use site ID to delete specific sites and manage your monitoring setup.

Instructions

Delete a site from Rybbit. This permanently removes the site and its replay data. Use rybbit_list_sites or rybbit_get_site_id to find site IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteIdYesSite ID (numeric ID or domain identifier)

Implementation Reference

  • The handler function for the rybbit_delete_site tool, which calls the client delete method.
    async ({ siteId }) => {
      try {
        const data = await client.delete<{ success: boolean }>(
          `/sites/${siteId}`
        );
    
        return {
          content: [
            {
              type: "text" as const,
              text: truncateResponse({
                message: `Site '${siteId}' deleted successfully`,
                ...data,
              }),
            },
          ],
        };
      } catch (err) {
        const message = err instanceof Error ? err.message : String(err);
        return {
  • The tool registration for rybbit_delete_site, including its schema and metadata.
    server.registerTool(
      "rybbit_delete_site",
      {
        title: "Delete Site",
        description:
          "Delete a site from Rybbit. This permanently removes the site and its replay data. Use rybbit_list_sites or rybbit_get_site_id to find site IDs.",
        inputSchema: {
          siteId: siteIdSchema,
        },
        annotations: {
          readOnlyHint: false,
          destructiveHint: true,
          idempotentHint: false,
          openWorldHint: true,
        },
      },
Behavior4/5

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

While annotations already flag destructiveHint=true, the description adds valuable specificity by clarifying that 'replay data' is also permanently destroyed, not just the site configuration. It correctly aligns with the destructive annotation without contradicting it.

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 well-structured sentences: action definition, consequence warning, and prerequisite guidance. Every sentence earns its place with zero redundancy or filler.

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?

For a single-parameter destructive operation without output schema, the description adequately covers the permanent data loss implications and parameter acquisition. It could be improved by mentioning error behavior (e.g., non-existent siteId) or confirmation requirements.

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?

With 100% schema description coverage (siteId is fully documented in the schema), the baseline is appropriately met. The description references 'site IDs' generally but does not add semantic details about the parameter format beyond what the schema already 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 opens with the specific verb 'Delete' paired with the resource 'site from Rybbit,' clearly distinguishing it from sibling tools like rybbit_create_site or rybbit_list_sites. The scope is immediately obvious.

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 explicitly names prerequisite tools (rybbit_list_sites or rybbit_get_site_id) to find the required siteId parameter, establishing a clear workflow. However, it lacks explicit 'when not to use' guidance or alternatives to deletion (e.g., disabling vs deleting).

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/nks-hub/rybbit-mcp'

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