Skip to main content
Glama

resume_site

Resume a suspended site on a specific server by providing the server ID and site ID. Restore access to a paused website with a single action.

Instructions

Resume a suspended site

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
server_idYesThe ID of the server
site_idYesThe ID of the site to resume

Implementation Reference

  • The 'resume_site' tool is registered on the MCP server via server.tool() with name 'resume_site', description 'Resume a suspended site', and input schema requiring server_id and site_id as numbers.
    server.tool(
      "resume_site",
      "Resume a suspended site",
      {
        server_id: z.coerce.number().describe("The ID of the server"),
        site_id: z.coerce.number().describe("The ID of the site to resume"),
      },
      async ({ server_id, site_id }) => {
        await client.resumeSite(server_id, site_id);
        return {
          content: [
            {
              type: "text" as const,
              text: `Site ${site_id} on server ${server_id} has been resumed`,
            },
          ],
        };
      }
    );
  • The handler function for 'resume_site' calls client.resumeSite(server_id, site_id) and returns a text response confirming the site has been resumed.
      async ({ server_id, site_id }) => {
        await client.resumeSite(server_id, site_id);
        return {
          content: [
            {
              type: "text" as const,
              text: `Site ${site_id} on server ${server_id} has been resumed`,
            },
          ],
        };
      }
    );
  • The client.resumeSite() method makes a POST request to /servers/{serverId}/sites/{siteId}/resume on the Ploi API to resume a suspended site.
    async resumeSite(serverId: number, siteId: number): Promise<void> {
      await this.request<void>(
        "POST",
        `/servers/${serverId}/sites/${siteId}/resume`
      );
    }
Behavior2/5

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

With no annotations, the description carries the full burden but only repeats the tool's name. It fails to disclose behavioral traits such as state changes, prerequisites (site must be suspended), or reversibility of the operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise at four words, but it omits necessary details like preconditions and effects. It is under-specified rather than efficiently compact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of annotations and an output schema, the description should explain preconditions (site must be suspended) and outcomes. It does not, making it incomplete for a simple mutation tool.

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 coverage is 100% with each parameter described. The description adds the phrase 'a suspended site' but does not enhance understanding beyond the schema. Baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Resume a suspended site' clearly states the verb (resume) and resource (site) with a condition (suspended), distinguishing it from the sibling 'suspend_site'. However, it could explicitly present itself as the inverse operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. It does not mention that the site must be suspended before resuming, nor does it provide context for typical use cases.

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/sudanese/ploi-mcp'

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