Skip to main content
Glama
harness

Harness MCP Server

Official
by harness
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

harness_update

DestructiveIdempotent

Update a Harness resource by submitting a new YAML/JSON definition or a Harness URL to auto-fill identifiers. Get a link to the updated resource.

Instructions

Update an existing Harness resource. For pipelines/input sets: pass body as a YAML string directly (recommended for complex definitions), or use body.yamlPipeline/body.pipeline. You can pass a Harness URL to auto-extract identifiers. Response includes openInHarness link to the updated resource when applicable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoA Harness UI URL — org, project, resource type, ID, and supported resource_scope are extracted automatically
bodyYesThe updated resource definition body. For pipelines: pass a YAML string directly, or an object with yamlPipeline (YAML string) or pipeline (JSON object)
org_idNoOrganization identifier. Required for org- and project-scoped resources unless a Harness URL is passed. This session has no configured default (common in hosted/multi-user HTTP) — pass the current org_id on the first call. Do not omit it.
paramsNoAdditional identifiers (e.g. pipeline_id for triggers/input sets, version_label for templates).
confirmNoSet to true to confirm the operation. Only required when the operation risk is medium_write or above AND the client cannot surface a confirmation prompt — e.g. managed MCP that does not advertise elicitation, or an elicitation that fails at runtime. Has no effect for low-risk updates. Does NOT override an explicit decline from a client that completed an elicitation prompt — a user's decline is authoritative.
project_idNoProject identifier. Required for project-scoped resources unless a Harness URL is passed. This session has no configured default (common in hosted/multi-user HTTP) — pass the current project_id on the first call. Do not omit it.
resource_idNoThe identifier of the resource to update. Optional when url contains the resource ID.
resource_typeYesThe type of resource to update
resource_scopeNoScope for the operation. account: account-level resources only — do not use account to skip a known org/project. org: org-level (org_id). project: org+project. Omit to use the resource's default scope. Auto-detected from url when present.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changedv3.2.22
    • changedInput schema / properties / org_id / description
      Previous value: -"Organization identifier (overrides default)"New value: +"Organization identifier. Required for org- and project-scoped resources unless a Harness URL is passed. This session has no configured default (common in hosted/multi-user HTTP) — pass the current org_id on the first call. Do not omit it."
    • changedInput schema / properties / project_id / description
      Previous value: -"Project identifier (overrides default)"New value: +"Project identifier. Required for project-scoped resources unless a Harness URL is passed. This session has no configured default (common in hosted/multi-user HTTP) — pass the current project_id on the first call. Do not omit it."
    • changedInput schema / properties / resource_scope / description
      Previous value: -"Scope for the operation. account: omit org/project (e.g. /v1/templates). org: org only. project: org+project. Auto-detected from url when present."New value: +"Scope for the operation. account: account-level resources only — do not use account to skip a known org/project. org: org-level (org_id). project: org+project. Omit to use the resource's default scope. Auto-detected from url when present."
    • changedInput schema / properties / resource_type / enum
      Previous value: -[
-  "agent",
-  "chaos_hub",
-  "chaos_input_set",
-  "chaos_loadtest",
-  "chaos_risk_scan",
-  "chaos_service",
-  "connector",
-  "cost_budget",
-  "cost_budget_group",
-  "cost_category",
-  "cost_perspective",
-  "cost_perspective_folder",
-  "database_instance",
-  "database_schema",
-  "environment",
-  "eval_annotation",
-  "eval_dataset",
-  "eval_dataset_item",
-  "eval_git_settings",
-  "eval_metric",
-  "eval_metric_set",
-  "eval_metric_set_entry",
-  "eval_registry_item",
-  "eval_suite",
-  "eval_target",
-  "evaluation",
-  "file_store",
-  "fme_environment",
-  "fme_feature_flag",
-  "fme_feature_flag_definition",
-  "fme_identity",
-  "fme_rule_based_segment_definition",
-  "fme_segment_definition",
-  "fme_segment_keys",
-  "freeze_window",
-  "gitops_application",
-  "gitops_applicationset",
-  "iacm_module",
-  "iacm_provider",
-  "iacm_variable_set",
-  "iacm_workspace",
-  "idp_entity",
-  "incident",
-  "infrastructure",
-  "input_set",
-  "organization",
-  "pipeline",
-  "pipeline_v1",
-  "policy",
-  "policy_set",
-  "pr_comment",
-  "project",
-  "pull_request",
-  "release_activity",
-  "release_process",
-  "repo_rule",
-  "repository",
-  "scorecard",
-  "scorecard_check",
-  "scs_auto_pr_config",
-  "service",
-  "service_override",
-  "space_rule",
-  "template",
-  "template_v1",
-  "trigger",
-  "unit_metric"
-]New value: +[
+  "agent",
+  "alert",
+  "chaos_hub",
+  "chaos_input_set",
+  "chaos_loadtest",
+  "chaos_risk_scan",
+  "chaos_service",
+  "connector",
+  "cost_budget",
+  "cost_budget_group",
+  "cost_category",
+  "cost_perspective",
+  "cost_perspective_folder",
+  "database_instance",
+  "database_schema",
+  "environment",
+  "eval_annotation",
+  "eval_dataset",
+  "eval_dataset_item",
+  "eval_git_settings",
+  "eval_metric",
+  "eval_metric_set",
+  "eval_metric_set_entry",
+  "eval_registry_item",
+  "eval_suite",
+  "eval_target",
+  "evaluation",
+  "file_store",
+  "fme_environment",
+  "fme_feature_flag",
+  "fme_feature_flag_definition",
+  "fme_identity",
+  "fme_rule_based_segment_definition",
+  "fme_segment_definition",
+  "fme_segment_keys",
+  "freeze_window",
+  "gitops_application",
+  "gitops_applicationset",
+  "iacm_module",
+  "iacm_provider",
+  "iacm_variable_set",
+  "iacm_workspace",
+  "idp_entity",
+  "incident",
+  "infrastructure",
+  "input_set",
+  "organization",
+  "pipeline",
+  "pipeline_v1",
+  "policy",
+  "policy_set",
+  "pr_comment",
+  "project",
+  "pull_request",
+  "release_activity",
+  "release_process",
+  "repo_rule",
+  "repository",
+  "scorecard",
+  "scorecard_check",
+  "scs_auto_pr_config",
+  "service",
+  "service_override",
+  "space_rule",
+  "template",
+  "template_v1",
+  "trigger",
+  "unit_metric"
+]
  2. Changed1 schema field changedv3.2.21
    • changedInput schema / properties / resource_type / enum
      Previous value: -[
-  "agent",
-  "chaos_hub",
-  "chaos_input_set",
-  "chaos_loadtest",
-  "chaos_risk_scan",
-  "chaos_service",
-  "connector",
-  "cost_budget",
-  "cost_budget_group",
-  "cost_category",
-  "cost_perspective",
-  "cost_perspective_folder",
-  "database_instance",
-  "database_schema",
-  "environment",
-  "eval_annotation",
-  "eval_dataset",
-  "eval_dataset_item",
-  "eval_git_settings",
-  "eval_metric",
-  "eval_metric_set",
-  "eval_metric_set_entry",
-  "eval_registry_item",
-  "eval_suite",
-  "eval_target",
-  "evaluation",
-  "file_store",
-  "fme_feature_flag",
-  "fme_feature_flag_definition",
-  "fme_identity",
-  "fme_rule_based_segment_definition",
-  "fme_segment_definition",
-  "fme_segment_keys",
-  "freeze_window",
-  "gitops_application",
-  "gitops_applicationset",
-  "iacm_module",
-  "iacm_variable_set",
-  "iacm_workspace",
-  "idp_entity",
-  "incident",
-  "infrastructure",
-  "input_set",
-  "organization",
-  "pipeline",
-  "pipeline_v1",
-  "policy",
-  "policy_set",
-  "pr_comment",
-  "project",
-  "pull_request",
-  "repo_rule",
-  "repository",
-  "scorecard",
-  "scorecard_check",
-  "scs_auto_pr_config",
-  "service",
-  "service_override",
-  "space_rule",
-  "template",
-  "template_v1",
-  "trigger",
-  "unit_metric"
-]New value: +[
+  "agent",
+  "chaos_hub",
+  "chaos_input_set",
+  "chaos_loadtest",
+  "chaos_risk_scan",
+  "chaos_service",
+  "connector",
+  "cost_budget",
+  "cost_budget_group",
+  "cost_category",
+  "cost_perspective",
+  "cost_perspective_folder",
+  "database_instance",
+  "database_schema",
+  "environment",
+  "eval_annotation",
+  "eval_dataset",
+  "eval_dataset_item",
+  "eval_git_settings",
+  "eval_metric",
+  "eval_metric_set",
+  "eval_metric_set_entry",
+  "eval_registry_item",
+  "eval_suite",
+  "eval_target",
+  "evaluation",
+  "file_store",
+  "fme_environment",
+  "fme_feature_flag",
+  "fme_feature_flag_definition",
+  "fme_identity",
+  "fme_rule_based_segment_definition",
+  "fme_segment_definition",
+  "fme_segment_keys",
+  "freeze_window",
+  "gitops_application",
+  "gitops_applicationset",
+  "iacm_module",
+  "iacm_provider",
+  "iacm_variable_set",
+  "iacm_workspace",
+  "idp_entity",
+  "incident",
+  "infrastructure",
+  "input_set",
+  "organization",
+  "pipeline",
+  "pipeline_v1",
+  "policy",
+  "policy_set",
+  "pr_comment",
+  "project",
+  "pull_request",
+  "release_activity",
+  "release_process",
+  "repo_rule",
+  "repository",
+  "scorecard",
+  "scorecard_check",
+  "scs_auto_pr_config",
+  "service",
+  "service_override",
+  "space_rule",
+  "template",
+  "template_v1",
+  "trigger",
+  "unit_metric"
+]
  3. Changed1 schema field changedv3.2.20
    • changedInput schema / properties / resource_type / enum
      Previous value: -[
-  "agent",
-  "chaos_hub",
-  "chaos_input_set",
-  "chaos_risk_scan",
-  "connector",
-  "cost_category",
-  "cost_perspective",
-  "cost_perspective_folder",
-  "database_instance",
-  "database_schema",
-  "environment",
-  "eval_annotation",
-  "eval_dataset",
-  "eval_dataset_item",
-  "eval_git_settings",
-  "eval_metric",
-  "eval_metric_set",
-  "eval_metric_set_entry",
-  "eval_registry_item",
-  "eval_suite",
-  "eval_target",
-  "evaluation",
-  "file_store",
-  "fme_feature_flag",
-  "fme_feature_flag_definition",
-  "fme_identity",
-  "fme_rule_based_segment_definition",
-  "fme_segment_keys",
-  "freeze_window",
-  "gitops_application",
-  "gitops_applicationset",
-  "idp_entity",
-  "incident",
-  "infrastructure",
-  "input_set",
-  "organization",
-  "pipeline",
-  "pipeline_v1",
-  "policy",
-  "policy_set",
-  "pr_comment",
-  "project",
-  "pull_request",
-  "repo_rule",
-  "repository",
-  "scorecard",
-  "scorecard_check",
-  "scs_auto_pr_config",
-  "service",
-  "service_override",
-  "space_rule",
-  "template",
-  "template_v1",
-  "trigger",
-  "unit_metric"
-]New value: +[
+  "agent",
+  "chaos_hub",
+  "chaos_input_set",
+  "chaos_loadtest",
+  "chaos_risk_scan",
+  "chaos_service",
+  "connector",
+  "cost_budget",
+  "cost_budget_group",
+  "cost_category",
+  "cost_perspective",
+  "cost_perspective_folder",
+  "database_instance",
+  "database_schema",
+  "environment",
+  "eval_annotation",
+  "eval_dataset",
+  "eval_dataset_item",
+  "eval_git_settings",
+  "eval_metric",
+  "eval_metric_set",
+  "eval_metric_set_entry",
+  "eval_registry_item",
+  "eval_suite",
+  "eval_target",
+  "evaluation",
+  "file_store",
+  "fme_feature_flag",
+  "fme_feature_flag_definition",
+  "fme_identity",
+  "fme_rule_based_segment_definition",
+  "fme_segment_definition",
+  "fme_segment_keys",
+  "freeze_window",
+  "gitops_application",
+  "gitops_applicationset",
+  "iacm_module",
+  "iacm_variable_set",
+  "iacm_workspace",
+  "idp_entity",
+  "incident",
+  "infrastructure",
+  "input_set",
+  "organization",
+  "pipeline",
+  "pipeline_v1",
+  "policy",
+  "policy_set",
+  "pr_comment",
+  "project",
+  "pull_request",
+  "repo_rule",
+  "repository",
+  "scorecard",
+  "scorecard_check",
+  "scs_auto_pr_config",
+  "service",
+  "service_override",
+  "space_rule",
+  "template",
+  "template_v1",
+  "trigger",
+  "unit_metric"
+]
  4. Changed1 schema field changedv3.2.17
    • changedInput schema / properties / resource_type / enum
      Previous value: -[
-  "agent",
-  "chaos_hub",
-  "chaos_input_set",
-  "connector",
-  "cost_category",
-  "cost_perspective",
-  "cost_perspective_folder",
-  "database_instance",
-  "database_schema",
-  "environment",
-  "eval_annotation",
-  "eval_dataset",
-  "eval_dataset_item",
-  "eval_git_settings",
-  "eval_metric",
-  "eval_metric_set",
-  "eval_metric_set_entry",
-  "eval_registry_item",
-  "eval_suite",
-  "eval_target",
-  "evaluation",
-  "file_store",
-  "fme_feature_flag",
-  "fme_feature_flag_definition",
-  "fme_identity",
-  "fme_rule_based_segment_definition",
-  "fme_segment_keys",
-  "freeze_window",
-  "gitops_application",
-  "gitops_applicationset",
-  "idp_entity",
-  "incident",
-  "infrastructure",
-  "input_set",
-  "organization",
-  "pipeline",
-  "pipeline_v1",
-  "policy",
-  "policy_set",
-  "pr_comment",
-  "project",
-  "pull_request",
-  "repo_rule",
-  "repository",
-  "scorecard",
-  "scorecard_check",
-  "scs_auto_pr_config",
-  "service",
-  "service_override",
-  "space_rule",
-  "template",
-  "template_v1",
-  "trigger",
-  "unit_metric"
-]New value: +[
+  "agent",
+  "chaos_hub",
+  "chaos_input_set",
+  "chaos_risk_scan",
+  "connector",
+  "cost_category",
+  "cost_perspective",
+  "cost_perspective_folder",
+  "database_instance",
+  "database_schema",
+  "environment",
+  "eval_annotation",
+  "eval_dataset",
+  "eval_dataset_item",
+  "eval_git_settings",
+  "eval_metric",
+  "eval_metric_set",
+  "eval_metric_set_entry",
+  "eval_registry_item",
+  "eval_suite",
+  "eval_target",
+  "evaluation",
+  "file_store",
+  "fme_feature_flag",
+  "fme_feature_flag_definition",
+  "fme_identity",
+  "fme_rule_based_segment_definition",
+  "fme_segment_keys",
+  "freeze_window",
+  "gitops_application",
+  "gitops_applicationset",
+  "idp_entity",
+  "incident",
+  "infrastructure",
+  "input_set",
+  "organization",
+  "pipeline",
+  "pipeline_v1",
+  "policy",
+  "policy_set",
+  "pr_comment",
+  "project",
+  "pull_request",
+  "repo_rule",
+  "repository",
+  "scorecard",
+  "scorecard_check",
+  "scs_auto_pr_config",
+  "service",
+  "service_override",
+  "space_rule",
+  "template",
+  "template_v1",
+  "trigger",
+  "unit_metric"
+]
  5. First observedv3.2.10

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds useful context about passing a Harness URL for identifier extraction and the openInHarness response link. It does not disclose overwrite consequences, confirmation expectations, or failure behavior, so the destructive nature is only partially explained beyond the annotations.

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 three sentences with no filler. It front-loads the core purpose, then gives the most important usage variation, a shortcut, and the response link. Every sentence earns its place.

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?

Given the 9-parameter schema, output schema, and safety annotations, the tool is well-covered. The description provides the key behavioral notes, while the schema handles default-scope, confirm, and identifier details. It could be even more complete with explicit create/delete routing, but that gap is minor.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds practical value by recommending a YAML string for complex pipeline/input-set definitions and noting URL-based auto-extraction of identifiers, which goes beyond the schema's per-parameter text. It does not need to enumerate every parameter.

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 states a clear verb and resource: 'Update an existing Harness resource.' It also gives concrete body-format guidance for pipelines/input sets, which helps disambiguate this from harness_create or harness_delete. It does not explicitly name those sibling tools, so it falls short of full differentiation.

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?

The word 'existing' implies this is for modifying resources that already exist, and the pipeline/input-set body guidance provides useful procedural direction. However, the description does not explicitly say when to prefer this over harness_create or harness_delete, nor does it name alternatives or exclusions.

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/harness/mcp-server'

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