Skip to main content
Glama

revert_staging_site

Roll back a staging site to an earlier version using content and staging site IDs to undo recent changes or restore previous configurations.

Instructions

Revert a staging site to a previous state

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentSiteIdYesContent site ID
reasonNoReason for reversion
stagingSiteIdYesStaging site ID

Implementation Reference

  • src/index.ts:1272-1308 (registration)
    Registration of the 'revert_staging_site' tool, including schema and handler function that calls the backend API to revert a staging site.
      "revert_staging_site",
      {
        title: "Revert Staging Site",
        description: "Revert a staging site to a previous state",
        inputSchema: {
          contentSiteId: z.string().describe("Content site ID"),
          stagingSiteId: z.string().describe("Staging site ID"),
          reason: z.string().optional().describe("Reason for reversion"),
        },
      },
      async ({ contentSiteId, stagingSiteId, reason }) => {
        try {
          const payload = { reason };
          const response: AxiosResponse<ApiResponse> = await apiClient.put(`/tools/content-sites/${contentSiteId}/staging-sites/${stagingSiteId}/revert`, payload);
    
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(response.data, null, 2),
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: handleApiError(error),
              },
            ],
            isError: true,
          };
        }
      }
    );
  • The handler executes the tool logic by making a PUT request to the Headlesshost API endpoint to revert the specified staging site, handling the response or error appropriately.
      try {
        const payload = { reason };
        const response: AxiosResponse<ApiResponse> = await apiClient.put(`/tools/content-sites/${contentSiteId}/staging-sites/${stagingSiteId}/revert`, payload);
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(response.data, null, 2),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: handleApiError(error),
            },
          ],
          isError: true,
        };
      }
    }
  • Input schema defining parameters: contentSiteId (required string), stagingSiteId (required string), reason (optional string). Uses Zod for validation.
      title: "Revert Staging Site",
      description: "Revert a staging site to a previous state",
      inputSchema: {
        contentSiteId: z.string().describe("Content site ID"),
        stagingSiteId: z.string().describe("Staging site ID"),
        reason: z.string().optional().describe("Reason for reversion"),
      },
    },

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/Headlesshost/mcp-server'

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