Skip to main content
Glama

mcp_install_theme_zip

Installs a WordPress theme from a ZIP using a public URL or a local file, with optional activation and guarded replacement of the active theme.

Instructions

Install a theme from a ZIP, either a public URL (url, must end in .zip) or a local file (file_path, absolute path to a .zip, max 64 MB). Give exactly one of them. file_path uploads the file from this machine, so it works for private or locally built themes; it needs cvrt-mcp-endpoints >= 1.20.0 on the site. Replacing the ACTIVE theme additionally needs replace_active: true (replaces the live theme; a theme with broken PHP takes the site down). url keeps working on older versions, but has no GitHub token support: private release assets cannot be installed that way.

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": {
      "site": "<site>"
    },
    "name": "mcp_install_theme_zip"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoURL to the theme ZIP file (must end in .zip). Not together with file_path.
siteYesSite id (see list_sites)
activateNoSwitch to the theme after install (default false)
file_pathNoAbsolute local path to a theme .zip to upload (max 64 MB). Not together with url.
overwriteNoReplace the theme folder if it already exists (default true). The ACTIVE theme is only replaced when replace_active is also true.
replace_activeNoAllow replacing the ACTIVE theme (default false; without it the site answers 409 active_theme). Replaces the live theme: a theme with broken PHP takes the site down. cvrt-mcp-endpoints >= 1.20.0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv3.14.0
    • changedInput schema / properties / activate / description
      Previous value: -"Activate after install"New value: +"Switch to the theme after install (default false)"
    • addedInput schema / properties / file_path
      Added value: +{
      +  "description": "Absolute local path to a theme .zip to upload (max 64 MB). Not together with url.",
      +  "type": "string"
      +}
    • changedInput schema / properties / overwrite / description
      Previous value: -"Overwrite if theme already exists"New value: +"Replace the theme folder if it already exists (default true). The ACTIVE theme is only replaced when replace_active is also true."
    • addedInput schema / properties / replace_active
      Added value: +{
      +  "default": false,
      +  "description": "Allow replacing the ACTIVE theme (default false; without it the site answers 409 active_theme). Replaces the live theme: a theme with broken PHP takes the site down. cvrt-mcp-endpoints >= 1.20.0.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / url / description
      Previous value: -"URL to theme ZIP file"New value: +"URL to the theme ZIP file (must end in .zip). Not together with file_path."
    • changedInput schema / required
      Previous value: -[
      -  "site",
      -  "url"
      -]New value: +[
      +  "site"
      +]
  2. Changed2 schema fields changedv3.4.0
    • addedInput schema / properties / site
      Added value: +{
      +  "description": "Site id (see list_sites)",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "url"
      -]New value: +[
      +  "site",
      +  "url"
      +]
  3. First observedv2.0.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the 64 MB cap, the cvrt-mcp-endpoints >= 1.20.0 requirement for file_path, that replace_active replaces the live theme and that broken PHP can take the site down, plus the GitHub token limitation for url. Gaps remain on authentication/permission requirements and no explicit statement of what is returned or persisted on success.

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?

Front-loads the core action and the url/file_path choice before the caveats, and every sentence carries operational information (size limit, version gate, active-theme risk, token limitation). It is dense but slightly run-on in places, which keeps it from a 5.

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 six-parameter, annotation-free mutation tool with no output schema, the description covers the essential decision points: exactly one source, private/local upload path, version requirement, and the dangerous active-theme replacement. Missing pieces like auth requirements and success behavior are minor relative to the risk disclosure it already provides.

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 already 100%, so the schema documents all six parameters and the baseline is 3. The description adds some value by explaining that file_path uploads from 'this machine' and its version prerequisite, and that url lacks GitHub token support, but it doesn't clarify the overwrite/activate interactions beyond what the schema says.

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?

States a specific verb+resource ('Install a theme from a ZIP') and immediately names its two input modes, which distinguishes it from a generic theme installer. It doesn't explicitly contrast with the sibling 'mcp_install_theme' (presumably slug/repo-based), leaving the agent to infer that distinction, so it stops short of 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 Guidelines4/5

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

Gives clear selection guidance between url and file_path ('private or locally built themes' need file_path; private GitHub release assets cannot go via url) and enforces mutual exclusivity with 'Give exactly one of them.' It doesn't state when to prefer this tool over mcp_install_theme or a repo-based install, so it lacks explicit alternative routing.

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