Harness MCP Server

Official

Overview Schema Related Servers Score Discussions

harness_delete

DestructiveIdempotent

Permanently delete a Harness resource by passing its URL to auto-extract identifiers. Confirmation is required to complete this irreversible removal.

Instructions

Delete a Harness resource. You can pass a Harness URL to auto-extract identifiers. This is destructive and cannot be undone.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	No	A Harness UI URL — org, project, resource type, ID, and supported resource_scope are extracted automatically
`org_id`	No	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.
`params`	No	Additional identifiers for nested resources (e.g. pipeline_id for triggers/input sets, environment_id for infrastructure).
`confirm`	No	Set to true to confirm the destructive operation. Required when the client cannot surface a confirmation prompt — e.g. managed MCP that does not advertise elicitation, or an elicitation that fails at runtime. Does NOT override an explicit decline from a client that completed an elicitation prompt — a user's decline is authoritative.
`project_id`	No	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.
`resource_id`	No	The identifier of the resource to delete. Optional when url contains the resource ID.
`resource_type`	Yes	The type of resource to delete
`resource_scope`	No	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.

Output Schema

TableJSON Schema

Name	Required	Description
`deleted`	Yes	Whether the resource was successfully deleted
`details`	No	Optional API response payload (e.g. template-service delete body)
`resource_id`	Yes	The ID of the deleted resource
`resource_type`	Yes	The type of resource that was deleted
`version_label`	No	Deleted template version label, when applicable

Schema Changelog

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

Changed3 schema fields changedv3.2.22Sep 1, 2026

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."

Changed1 schema field changedv3.2.21Aug 26, 2026

changedInput schema / properties / resource_type / enum

Previous value: -[
-  "agent",
-  "branch",
-  "chaos_action",
-  "chaos_action_template",
-  "chaos_experiment",
-  "chaos_experiment_template",
-  "chaos_fault",
-  "chaos_fault_template",
-  "chaos_guard_condition",
-  "chaos_guard_rule",
-  "chaos_hub",
-  "chaos_input_set",
-  "chaos_loadtest",
-  "chaos_probe",
-  "chaos_probe_template",
-  "chaos_risk_scan",
-  "chaos_service",
-  "connector",
-  "cost_budget",
-  "cost_budget_group",
-  "cost_category",
-  "cost_perspective",
-  "cost_perspective_folder",
-  "database_instance",
-  "database_schema",
-  "delegate_token",
-  "environment",
-  "eval_annotation",
-  "eval_dataset",
-  "eval_dataset_item",
-  "eval_metric",
-  "eval_metric_set",
-  "eval_metric_set_entry",
-  "eval_registry_item",
-  "eval_suite",
-  "eval_suite_evaluation",
-  "eval_target",
-  "evaluation",
-  "file_store",
-  "fme_feature_flag",
-  "fme_rule_based_segment",
-  "fme_segment",
-  "fme_segment_definition",
-  "freeze_window",
-  "gitops_agent",
-  "gitops_application",
-  "gitops_applicationset",
-  "gitops_cluster",
-  "gitops_cluster_link",
-  "gitops_repo_credential",
-  "gitops_repository",
-  "infrastructure",
-  "input_set",
-  "organization",
-  "pipeline",
-  "pipeline_v1",
-  "policy",
-  "policy_set",
-  "pr_comment",
-  "project",
-  "repo_rule",
-  "resource_group",
-  "role",
-  "role_assignment",
-  "service",
-  "service_account",
-  "service_override",
-  "space_rule",
-  "tag",
-  "template",
-  "template_v1",
-  "trigger",
-  "unit_metric",
-  "user_group"
-]New value: +[
+  "agent",
+  "branch",
+  "chaos_action",
+  "chaos_action_template",
+  "chaos_experiment",
+  "chaos_experiment_template",
+  "chaos_fault",
+  "chaos_fault_template",
+  "chaos_guard_condition",
+  "chaos_guard_rule",
+  "chaos_hub",
+  "chaos_input_set",
+  "chaos_loadtest",
+  "chaos_probe",
+  "chaos_probe_template",
+  "chaos_risk_scan",
+  "chaos_service",
+  "connector",
+  "cost_budget",
+  "cost_budget_group",
+  "cost_category",
+  "cost_perspective",
+  "cost_perspective_folder",
+  "database_instance",
+  "database_schema",
+  "delegate_token",
+  "environment",
+  "eval_annotation",
+  "eval_dataset",
+  "eval_dataset_item",
+  "eval_metric",
+  "eval_metric_set",
+  "eval_metric_set_entry",
+  "eval_registry_item",
+  "eval_suite",
+  "eval_suite_evaluation",
+  "eval_target",
+  "evaluation",
+  "file_store",
+  "fme_environment",
+  "fme_feature_flag",
+  "fme_feature_flag_definition",
+  "fme_rule_based_segment",
+  "fme_segment",
+  "fme_segment_definition",
+  "freeze_window",
+  "gitops_agent",
+  "gitops_application",
+  "gitops_applicationset",
+  "gitops_cluster",
+  "gitops_cluster_link",
+  "gitops_repo_credential",
+  "gitops_repository",
+  "infrastructure",
+  "input_set",
+  "organization",
+  "pipeline",
+  "pipeline_v1",
+  "policy",
+  "policy_set",
+  "pr_comment",
+  "project",
+  "release_activity",
+  "release_process",
+  "repo_rule",
+  "resource_group",
+  "role",
+  "role_assignment",
+  "service",
+  "service_account",
+  "service_override",
+  "space_rule",
+  "tag",
+  "template",
+  "template_v1",
+  "trigger",
+  "unit_metric",
+  "user_group"
+]

Changed1 schema field changedv3.2.20Aug 19, 2026

changedInput schema / properties / resource_type / enum

Previous value: -[
-  "agent",
-  "branch",
-  "chaos_action",
-  "chaos_action_template",
-  "chaos_experiment",
-  "chaos_experiment_template",
-  "chaos_fault",
-  "chaos_fault_template",
-  "chaos_guard_condition",
-  "chaos_guard_rule",
-  "chaos_hub",
-  "chaos_input_set",
-  "chaos_loadtest",
-  "chaos_probe",
-  "chaos_probe_template",
-  "chaos_risk_scan",
-  "connector",
-  "cost_category",
-  "cost_perspective",
-  "cost_perspective_folder",
-  "database_instance",
-  "database_schema",
-  "delegate_token",
-  "environment",
-  "eval_annotation",
-  "eval_dataset",
-  "eval_dataset_item",
-  "eval_metric",
-  "eval_metric_set",
-  "eval_metric_set_entry",
-  "eval_registry_item",
-  "eval_suite",
-  "eval_suite_evaluation",
-  "eval_target",
-  "evaluation",
-  "file_store",
-  "fme_feature_flag",
-  "fme_rule_based_segment",
-  "freeze_window",
-  "gitops_agent",
-  "gitops_application",
-  "gitops_applicationset",
-  "gitops_cluster",
-  "gitops_cluster_link",
-  "gitops_repo_credential",
-  "gitops_repository",
-  "infrastructure",
-  "input_set",
-  "organization",
-  "pipeline",
-  "pipeline_v1",
-  "policy",
-  "policy_set",
-  "pr_comment",
-  "project",
-  "repo_rule",
-  "resource_group",
-  "role",
-  "role_assignment",
-  "service",
-  "service_account",
-  "service_override",
-  "space_rule",
-  "tag",
-  "template",
-  "template_v1",
-  "trigger",
-  "unit_metric",
-  "user_group"
-]New value: +[
+  "agent",
+  "branch",
+  "chaos_action",
+  "chaos_action_template",
+  "chaos_experiment",
+  "chaos_experiment_template",
+  "chaos_fault",
+  "chaos_fault_template",
+  "chaos_guard_condition",
+  "chaos_guard_rule",
+  "chaos_hub",
+  "chaos_input_set",
+  "chaos_loadtest",
+  "chaos_probe",
+  "chaos_probe_template",
+  "chaos_risk_scan",
+  "chaos_service",
+  "connector",
+  "cost_budget",
+  "cost_budget_group",
+  "cost_category",
+  "cost_perspective",
+  "cost_perspective_folder",
+  "database_instance",
+  "database_schema",
+  "delegate_token",
+  "environment",
+  "eval_annotation",
+  "eval_dataset",
+  "eval_dataset_item",
+  "eval_metric",
+  "eval_metric_set",
+  "eval_metric_set_entry",
+  "eval_registry_item",
+  "eval_suite",
+  "eval_suite_evaluation",
+  "eval_target",
+  "evaluation",
+  "file_store",
+  "fme_feature_flag",
+  "fme_rule_based_segment",
+  "fme_segment",
+  "fme_segment_definition",
+  "freeze_window",
+  "gitops_agent",
+  "gitops_application",
+  "gitops_applicationset",
+  "gitops_cluster",
+  "gitops_cluster_link",
+  "gitops_repo_credential",
+  "gitops_repository",
+  "infrastructure",
+  "input_set",
+  "organization",
+  "pipeline",
+  "pipeline_v1",
+  "policy",
+  "policy_set",
+  "pr_comment",
+  "project",
+  "repo_rule",
+  "resource_group",
+  "role",
+  "role_assignment",
+  "service",
+  "service_account",
+  "service_override",
+  "space_rule",
+  "tag",
+  "template",
+  "template_v1",
+  "trigger",
+  "unit_metric",
+  "user_group"
+]

Changed1 schema field changedv3.2.17Aug 4, 2026

changedInput schema / properties / resource_type / enum

Previous value: -[
-  "agent",
-  "branch",
-  "chaos_action",
-  "chaos_action_template",
-  "chaos_experiment",
-  "chaos_experiment_template",
-  "chaos_fault",
-  "chaos_fault_template",
-  "chaos_guard_condition",
-  "chaos_guard_rule",
-  "chaos_hub",
-  "chaos_input_set",
-  "chaos_loadtest",
-  "chaos_probe",
-  "chaos_probe_template",
-  "connector",
-  "cost_category",
-  "cost_perspective",
-  "cost_perspective_folder",
-  "database_instance",
-  "database_schema",
-  "delegate_token",
-  "environment",
-  "eval_annotation",
-  "eval_dataset",
-  "eval_dataset_item",
-  "eval_metric",
-  "eval_metric_set",
-  "eval_metric_set_entry",
-  "eval_registry_item",
-  "eval_suite",
-  "eval_suite_evaluation",
-  "eval_target",
-  "evaluation",
-  "file_store",
-  "fme_feature_flag",
-  "fme_rule_based_segment",
-  "freeze_window",
-  "gitops_agent",
-  "gitops_application",
-  "gitops_applicationset",
-  "gitops_cluster",
-  "gitops_cluster_link",
-  "gitops_repo_credential",
-  "gitops_repository",
-  "infrastructure",
-  "input_set",
-  "organization",
-  "pipeline",
-  "pipeline_v1",
-  "policy",
-  "policy_set",
-  "pr_comment",
-  "project",
-  "repo_rule",
-  "resource_group",
-  "role",
-  "role_assignment",
-  "service",
-  "service_account",
-  "service_override",
-  "space_rule",
-  "tag",
-  "template",
-  "template_v1",
-  "trigger",
-  "unit_metric",
-  "user_group"
-]New value: +[
+  "agent",
+  "branch",
+  "chaos_action",
+  "chaos_action_template",
+  "chaos_experiment",
+  "chaos_experiment_template",
+  "chaos_fault",
+  "chaos_fault_template",
+  "chaos_guard_condition",
+  "chaos_guard_rule",
+  "chaos_hub",
+  "chaos_input_set",
+  "chaos_loadtest",
+  "chaos_probe",
+  "chaos_probe_template",
+  "chaos_risk_scan",
+  "connector",
+  "cost_category",
+  "cost_perspective",
+  "cost_perspective_folder",
+  "database_instance",
+  "database_schema",
+  "delegate_token",
+  "environment",
+  "eval_annotation",
+  "eval_dataset",
+  "eval_dataset_item",
+  "eval_metric",
+  "eval_metric_set",
+  "eval_metric_set_entry",
+  "eval_registry_item",
+  "eval_suite",
+  "eval_suite_evaluation",
+  "eval_target",
+  "evaluation",
+  "file_store",
+  "fme_feature_flag",
+  "fme_rule_based_segment",
+  "freeze_window",
+  "gitops_agent",
+  "gitops_application",
+  "gitops_applicationset",
+  "gitops_cluster",
+  "gitops_cluster_link",
+  "gitops_repo_credential",
+  "gitops_repository",
+  "infrastructure",
+  "input_set",
+  "organization",
+  "pipeline",
+  "pipeline_v1",
+  "policy",
+  "policy_set",
+  "pr_comment",
+  "project",
+  "repo_rule",
+  "resource_group",
+  "role",
+  "role_assignment",
+  "service",
+  "service_account",
+  "service_override",
+  "space_rule",
+  "tag",
+  "template",
+  "template_v1",
+  "trigger",
+  "unit_metric",
+  "user_group"
+]

Changed1 schema field changedv3.2.16Jul 29, 2026

changedInput schema / properties / resource_type / enum

Previous value: -[
-  "agent",
-  "branch",
-  "chaos_action",
-  "chaos_action_template",
-  "chaos_experiment",
-  "chaos_experiment_template",
-  "chaos_fault",
-  "chaos_fault_template",
-  "chaos_guard_condition",
-  "chaos_guard_rule",
-  "chaos_hub",
-  "chaos_input_set",
-  "chaos_loadtest",
-  "chaos_probe",
-  "chaos_probe_template",
-  "connector",
-  "cost_category",
-  "cost_perspective",
-  "cost_perspective_folder",
-  "database_instance",
-  "database_schema",
-  "delegate_token",
-  "environment",
-  "eval_annotation",
-  "eval_dataset",
-  "eval_dataset_item",
-  "eval_metric",
-  "eval_metric_set",
-  "eval_metric_set_entry",
-  "eval_registry_item",
-  "eval_suite",
-  "eval_suite_evaluation",
-  "eval_target",
-  "evaluation",
-  "file_store",
-  "fme_feature_flag",
-  "fme_rule_based_segment",
-  "freeze_window",
-  "gitops_cluster_link",
-  "infrastructure",
-  "input_set",
-  "organization",
-  "pipeline",
-  "pipeline_v1",
-  "policy",
-  "policy_set",
-  "pr_comment",
-  "project",
-  "repo_rule",
-  "resource_group",
-  "role",
-  "role_assignment",
-  "service",
-  "service_account",
-  "service_override",
-  "space_rule",
-  "tag",
-  "template",
-  "template_v1",
-  "trigger",
-  "unit_metric",
-  "user_group"
-]New value: +[
+  "agent",
+  "branch",
+  "chaos_action",
+  "chaos_action_template",
+  "chaos_experiment",
+  "chaos_experiment_template",
+  "chaos_fault",
+  "chaos_fault_template",
+  "chaos_guard_condition",
+  "chaos_guard_rule",
+  "chaos_hub",
+  "chaos_input_set",
+  "chaos_loadtest",
+  "chaos_probe",
+  "chaos_probe_template",
+  "connector",
+  "cost_category",
+  "cost_perspective",
+  "cost_perspective_folder",
+  "database_instance",
+  "database_schema",
+  "delegate_token",
+  "environment",
+  "eval_annotation",
+  "eval_dataset",
+  "eval_dataset_item",
+  "eval_metric",
+  "eval_metric_set",
+  "eval_metric_set_entry",
+  "eval_registry_item",
+  "eval_suite",
+  "eval_suite_evaluation",
+  "eval_target",
+  "evaluation",
+  "file_store",
+  "fme_feature_flag",
+  "fme_rule_based_segment",
+  "freeze_window",
+  "gitops_agent",
+  "gitops_application",
+  "gitops_applicationset",
+  "gitops_cluster",
+  "gitops_cluster_link",
+  "gitops_repo_credential",
+  "gitops_repository",
+  "infrastructure",
+  "input_set",
+  "organization",
+  "pipeline",
+  "pipeline_v1",
+  "policy",
+  "policy_set",
+  "pr_comment",
+  "project",
+  "repo_rule",
+  "resource_group",
+  "role",
+  "role_assignment",
+  "service",
+  "service_account",
+  "service_override",
+  "space_rule",
+  "tag",
+  "template",
+  "template_v1",
+  "trigger",
+  "unit_metric",
+  "user_group"
+]

First observedv3.2.10Jul 16, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already mark destructiveHint=true, and the description reinforces this with 'destructive and cannot be undone,' adding irreversibility context. It also discloses the URL auto-extraction behavior, though it does not mention confirmation requirements or side effects beyond deletion.

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?

Two short sentences, front-loaded with the core action. The irreversibility warning is the most important non-schema context and is placed at the end without padding.

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?

Complexity is high (8 params, nested objects, enums), but the schema is unusually rich and annotations cover the read/write/destructive profile. The description does not need to explain return values because an output schema exists. The only minor gap is that the confirm workflow is not surfaced in the description, though the schema documents it thoroughly.

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 the baseline is 3. The description's URL auto-extraction point is already captured in the url parameter's schema description. It does not add new parameter semantics beyond what the schema already provides.

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 opens with a specific verb and object, 'Delete a Harness resource,' clearly identifying this as the deletion tool among siblings like harness_create and harness_update. It also adds a distinguishing capability (URL auto-extraction), so an agent can select it without opening the schema.

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 description implies deletion usage but does not explicitly state when it should be chosen over sibling tools or when it should not be used. No alternatives are named, though the destructive warning provides some cautionary context.

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

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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