Skip to main content
Glama
Sign In
wp-ssh-mcp

wp-ssh-mcp

by MSSOFTPC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

template_export

template_export
Read-onlyIdempotent

Export a page's Elementor data and settings to copy to another site with template_import.

Instructions

Export a page's Elementor data + settings so it can be copied to another site with template_import.

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": {
      "post_id": "<post_id>"
    },
    "name": "template_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYesPost ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is clear. The description adds the export scope of data plus settings, but it does not describe the output format or any operational constraints, which matters because there is no output schema.

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?

The description is a single, front-loaded sentence with no wasted words. It states the action, scope, and intended follow-up tool efficiently.

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 simple one-parameter, read-only export tool with rich annotations, the description covers purpose and intended workflow. Its main remaining gap is not specifying what the export returns, but the companion template_import workflow compensates for most of that.

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% and there is only one required parameter, post_id, already documented as 'Post ID'. The description implies the parameter identifies a page, but adds no format or usage detail beyond the schema.

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 names a specific verb and resource: exporting a page's Elementor data plus settings. It also states the intended outcome, copying to another site with template_import, which helps distinguish it from a plain data-read tool, though it does not explicitly contrast with sibling elementor_data_get.

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 gives a clear use case: exporting a page's Elementor data and settings for transfer to another site via template_import. It does not provide explicit when-not guidance or contrast with other read-oriented siblings.

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