Skip to main content
Glama

CI/CD convert workflow to pipeline

cicd_convert_workflow_to_pipeline
Read-only

Convert a repository's existing CI definition - GitHub Actions workflows, a .gitlab-ci.yml, a bitbucket-pipelines.yml or a .circleci/config.yml - into an Ankra pipeline (.ankra/pipeline.yaml), the definition Ankra's own pipeline engine runs inside the cluster. Read the files first with github_read_file (or workspace_read_file) and pass their contents here. Returns the rendered pipeline_yaml, a notes list naming every construct the conversion could not carry across faithfully, and a validation verdict. This tool only PROPOSES text - it writes nothing to the repository; open a pull request with scm_create_pull_request (agent mode) or github_create_pull_request to land it. A converted pipeline is a starting point a person reviews, never a drop-in replacement: marketplace actions, Bitbucket pipes and CircleCI orb commands the mapping table knows become the matching Ankra stage or ankra/* step, and an unmappable third-party step becomes a stage that FAILS with an explanation rather than being silently dropped, so always show the user the notes. Bounded to 20 files and 256KB of content per call.

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": {
      "workflow_files": "<workflow_files>"
    },
    "name": "cicd_convert_workflow_to_pipeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoOPTIONAL. The source format. Omitted, it is inferred from the paths: a file named .gitlab-ci* selects gitlab_ci, a file named bitbucket-pipelines* selects bitbucket_pipelines, a path under .circleci/ selects circleci, anything else selects github_actions.
application_idNoOPTIONAL. The Ankra Application this repository belongs to. When it resolves, the converted pipeline's metadata.name is the application's name instead of one derived from the workflow; when it does not, the conversion still returns a pipeline and says so in the notes.
workflow_filesYesThe CI definition files to convert, with their repository paths. For GitHub Actions pass every workflow that participates in the build - they are converted into ONE pipeline, because a repository's workflows share one checkout and one run. For GitLab, Bitbucket and CircleCI pass exactly one file: the .gitlab-ci.yml, the bitbucket-pipelines.yml or the .circleci/config.yml.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, and the description substantially enriches that: it writes nothing to the repository, it returns pipeline_yaml plus a notes list plus a validation verdict, and unmappable third-party steps become stages that FAIL loudly rather than being silently dropped. It also discloses hard limits (20 files, 256KB per call). Only missing piece is any mention of latency or error behavior for malformed input, so not quite a 5.

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-loaded with purpose, then inputs, then return values, then safety caveats — a sensible order. It is dense but nearly every clause carries information; the 'starting point a person reviews' sentence is slightly repetitive with the following 'always show the user the notes' clause, which is the only real redundancy.

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?

No output schema exists, yet the description fully enumerates the return payload (rendered pipeline_yaml, notes list, validation verdict). Combined with the input-gathering prerequisite, the write-free guarantee, and the size limits, an agent has everything needed to call this correctly and to explain the result to a user.

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%, so baseline is 3, and most of the description's parameter guidance (pass real paths because notes attribute findings there; pass every GitHub workflow as ONE pipeline; pass exactly one file for GitLab/Bitbucket/CircleCI) duplicates the schema text verbatim. The one genuinely new datum is the 256KB content bound; the optional format and application_id parameters go unmentioned.

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?

States a specific verb (convert) plus both sides of the transformation: source formats (GitHub Actions, .gitlab-ci.yml, bitbucket-pipelines.yml, .circleci/config.yml) and target (.ankra/pipeline.yaml for Ankra's pipeline engine). This clearly separates it from siblings such as cicd_validate_workflow_yaml and cicd_propose_application_pipeline, which an agent can now rule out.

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

Usage Guidelines5/5

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

Gives an explicit prerequisite workflow (read files first with github_read_file or workspace_read_file, then pass contents here) and names the downstream alternatives for landing the result (scm_create_pull_request in agent mode, or github_create_pull_request). It also sets expectations that a human must review the output, which is a real usage constraint rather than filler.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.