Pull GitHub commits into a cPanel repository and run deployment tasks from .cpanel.yml to update hosted sites.
Pull latest commits from GitHub and execute deployment tasks configured in .cpanel.yml
| Name | Required | Description | Default |
|---|---|---|---|
| branch | No | Branch to pull and deploy | main |
| repository_root | Yes | cPanel repository path (e.g. '/home/user/repositories/mysite') |
Changes observed during successful MCP inspections.
v2.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the full burden. To its credit it discloses the actual mechanism: a network pull from GitHub followed by execution of whatever tasks .cpanel.yml defines, which tells the agent this is an arbitrary-code-execution deployment, not a plain fetch. It says nothing about whether working files are overwritten, rollback behavior, required auth, or what happens if .cpanel.yml is missing.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with the action first and the mechanism second; nothing is redundant or padded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a deployment mutation with no annotations and no output schema, the description covers the 'what' adequately but leaves the agent without knowledge of side effects, failure modes, or the shape of the result (e.g., whether a deploy log is returned). More context is warranted given the risk profile of the tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Both parameters are fully documented in the schema (100% coverage, including the default of 'main' and a path example), so the schema does the heavy lifting. The description adds no extra meaning about branch selection or valid repository_root values beyond what is already structured.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Uses two specific verbs (pull, execute deployment tasks) on a named resource, and the reference to '.cpanel.yml' makes the mechanism clear. It is distinguishable from mutation siblings like update_git_repo or deploy_git_repo, though it never explicitly contrasts itself with them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use or when-not-to-use guidance. With siblings such as connect_github_repo, update_git_repo, deploy_git_repo and get_git_deployment_status in the same family, the agent gets no signal about which one a given situation calls for, and no prerequisites (connected repo, configured token, existing .cpanel.yml) are stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.