ppdm-mcp-server

bulk_trigger_backup

Trigger on-demand backups for all assets matching an optional name or type filter under a specified policy, enabling bulk backup runs across your PowerProtect environment.

Instructions

Trigger on-demand backup for all assets matching an optional filter under a named policy.

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": {
      "policy_name": "<policy_name>"
    },
    "name": "bulk_trigger_backup"
  }
}

Input Schema

Name	Required	Description
`asset_name`	No	Filter assets by name substring
`asset_type`	No	Filter assets by type (e.g. KUBERNETES)
`policy_name`	Yes	Policy name — exact, or a partial name that matches only one policy

Schema Changelog

Changes observed during successful MCP inspections.

First observedv4.2.2Nov 11, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations accompany this side-effecting action tool, so the description must carry the full behavioral burden. It does not say whether the trigger is asynchronous, what is returned (job IDs?), whether the call is idempotent, or what happens when the filter matches zero assets or the partial policy name is ambiguous.

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?

A single front-loaded sentence with no filler; verb, scope, and policy context come in the right order. It is tight to the point of being under-specified, but no wording is wasted.

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 bulk, side-effecting action with no annotations and no output schema, the definition should say how results are reported (job handles, async completion) and how failures surface. Neither is covered, leaving real gaps for an agent that must call this correctly and then track the result.

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%, so each parameter is already documented, and the description adds only the framing that the asset filters are optional and that an empty filter means all assets. That is modest value over the schema rather than new semantics.

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?

Names a specific action (trigger on-demand backup) and a specific scope (all assets matching an optional filter, under a named policy). The word "bulk" in the name plus "all assets" signals how it differs from a single-asset backup tool, though the description never names that alternative.

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

Usage Guidelines3/5

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

"On-demand backup for all assets matching an optional filter" implies the bulk-trigger scenario well enough that an agent can infer when to reach for it. However, it never states when not to use it, nor does it point to a narrower sibling for single-asset backups, leaving the choice to inference.

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