Skip to main content
Glama
Sign In
EdgeOne Pages MCP

EdgeOne Pages MCP

by BACH-AI-Tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

deploy_folder_or_zip

Deploy built frontend folders or zip files to EdgeOne Pages for public web hosting with edge delivery capabilities.

Instructions

Deploy a built frontend directory (or zip file) to EdgeOne Pages. Returns: the deployment URL and project metadata.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "builtFolderPath": "<builtFolderPath>"
    },
    "name": "deploy_folder_or_zip"
  }
}

Input Schema

NameRequiredDescriptionDefault
builtFolderPathYesProvide the absolute path to the built frontend folder(or zip file) you wish to deploy.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.15

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a deployment operation (implying a write/mutation) and mentions return values, but doesn't cover critical aspects like authentication requirements, rate limits, error conditions, whether deployment is reversible, or what happens to existing deployments. For a mutation tool with zero annotation coverage, this leaves significant gaps.

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

Conciseness4/5

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

The description is appropriately concise with two sentences: one stating the action and one stating the return values. It's front-loaded with the core purpose. While efficient, it could be slightly more structured by separating usage guidance from return information.

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?

For a deployment/mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'deploy' entails operationally, what permissions are needed, how deployments are managed, or what the return metadata includes. The mention of return values is helpful but insufficient given the tool's complexity and lack of structured documentation.

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 schema already fully documents the single parameter. The description adds marginal value by reinforcing that it accepts 'built frontend folder (or zip file)' but doesn't provide additional syntax, format details, or constraints beyond what's in the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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 clearly states the action ('Deploy'), the resource ('built frontend directory (or zip file)'), and the target ('EdgeOne Pages'). It distinguishes from the sibling tool 'deploy_html' by specifying it handles directories/zip files rather than HTML content. However, it doesn't explicitly contrast with the sibling, keeping it at a 4 rather than a 5.

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?

The description provides no guidance on when to use this tool versus alternatives like 'deploy_html'. It mentions the return values but doesn't explain prerequisites, constraints, or appropriate contexts for deployment. There's no explicit when/when-not usage advice.

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

Deploy Server

Other Tools