Skip to main content
Glama
cloin

SemaphoreUI MCP Server

by cloin

run_task

Execute an Ansible task from a template with optional 30-second startup monitoring. Supports overrides for limit, inventory, environment, dry-run, and diff.

Instructions

Run a task from a template with optional 30-second monitoring.

Args: template_id: ID of the template to run project_id: Optional project ID (if not provided, will attempt to determine from template) environment: Optional environment variables for the task as dictionary limit: Restrict execution to specific hosts/groups (Ansible --limit) dry_run: Run without making changes (Ansible --check) diff: Show differences when changing files (Ansible --diff) debug: Enable verbose debug output playbook: Override playbook file path git_branch: Override git branch to use message: Task description/message arguments: Additional CLI arguments inventory_id: Override inventory to use follow: Enable 30-second monitoring for startup verification (default: False)

Returns: Task execution result with immediate web URLs and optional monitoring summary

Template Override Requirements: Some parameters require the template to have overrides enabled in task_params. Use create_template() or update_template() with task_params to enable:

- limit: requires task_params={"allow_override_limit": true}
- inventory_id: requires task_params={"allow_override_inventory": true}

Without these settings, the parameter will be ignored silently.

Examples: # Just start the task and get URLs result = await run_task(template_id=5)

# Start task with 30-second monitoring and get URLs
result = await run_task(template_id=5, follow=True)

# Run with limit to specific hosts (template must allow override)
result = await run_task(template_id=5, limit="webservers")

# Dry run with diff to preview changes
result = await run_task(template_id=5, dry_run=True, diff=True)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
template_idYes
project_idNo
environmentNo
limitNo
dry_runNo
diffNo
debugNo
playbookNo
git_branchNo
messageNo
argumentsNo
inventory_idNo
followNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that some parameters are silently ignored without template overrides, and that the tool returns immediate web URLs with optional monitoring summary. This adds behavioral context beyond the 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 well-organized with a summary, parameter list, return value, override requirements, and examples. Every section adds value without unnecessary repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (13 parameters, 1 required, output schema exists), the description thoroughly covers the input semantics, behavioral constraints, and provides practical examples. It is self-contained and leaves no major gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% documentation coverage, but the description provides detailed explanations for all 13 parameters, including default behavior and constraints. For example, it explains that project_id is optional and will be auto-determined if missing, and that limit requires a template override to work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description starts with a specific verb and resource: 'Run a task from a template with optional 30-second monitoring.' It clearly identifies the tool's action and scope, distinguishing it from sibling tools like list_tasks or create_template.

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 includes sections on template override requirements and multiple examples showing common use cases. However, it does not explicitly state when not to use this tool or provide alternatives for different scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cloin/semaphore-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server