Skip to main content
Glama
harness

Harness MCP Server

Official
by harness

harness_list

Read-only

List and filter Harness resources with pagination. Auto-detects scope and resource type from a Harness UI URL.

Instructions

List Harness resources with filtering and pagination. Accepts a Harness URL to auto-extract scope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoHarness UI URL — auto-extracts org, project, and type
pageNoPage number, 0-indexed
sizeNoPage size (1–100)
org_idNoOrganization identifier (overrides default)
paramsNoAdditional identifiers for nested resources (e.g. repo_id for pull requests). Call harness_describe for fields per resource_type.
compactNoStrip verbose metadata from list items, keeping only essential fields (default true)
filtersNoResource-specific filters as key-value pairs. Available keys across enabled resource types: search_term, module, filter_type, pipeline_id, status, branch, my_deployments, execution_id, approval_status, approval_type, node_execution_id, sort, order, env_type, type, category, connector_names, connector_identifiers, connectivity_statuses, connector_connectivity_modes, description, inheriting_credentials_from_delegate, tags, include_all_connectors_available_at_scope, environment_id, deployment_type, secret_identifier, secret_name, secret_manager_identifiers, include_all_secrets_accessible_at_scope, audit_resource_type, action, start_time, end_time, all, delegate_name, delegate_type, host_name, delegate_group_identifier, delegate_instance_filter, auto_upgrade, version_status, name, query, git_ref, path, since, until, committer, inherited, search, package_type, template_type, template_list_type, global, metadata_only, entity_type, folder_id, kind, scope_level, owned_by_me, favorites, owner, lifecycle, sort_type, sort_order, is_custom, entity_identifier, state, after, before, offset, workspace_id, rollout_status_id, segment_name, repo_creds_id, agent_id, app_name, namespace, resource_name, group, version, scope, experiment_name, infra_id, experiment_ids, start_date, end_date, target_network_map_ids, my_experiments, exclude_automation, probe_ids, infra_type, sort_field, sort_ascending, experiment_run_ids, notify_ids, hub_identity, infrastructure_type, infrastructure, include_all_scope, experiment_id, is_identity, include_legacy_infra, infra_scope, is_ai_enabled, is_enterprise, fault_id, permissions_required, only_templatised_faults, environment_type, minimal, agent_identity, cloud_filter, view_state, view_type, view_ids, folder_name_pattern, group_by, time_filter, limit, time_resolution, min_saving, perspective_id, anomaly_view, search_text, order_by_field, order_by_direction, min_amount, min_anomalous_spend, value_type, value_sub_type, is_cluster_query, is_cluster_hourly_data, search_key, page, size, aspect, integration_type, profile_id, team_ref_id, date_start, date_end, granularity, metric_type, artifact_type, source_id, artifact_id, dependency_type, oss_risk_filter, standards, enforcement_id, purl, drift_id, severity_codes, issue_types, target_ids, target_types, pipeline_ids, scan_tools, exemption_statuses, stages, steps, product_names, include_exempted, origins, origin_statuses, epss, epss_percentile, severity_overridden, reachability, exploitability, page_existing, page_size_existing, page_new, page_size_new, migration_type, dbschema_id, dbinstance_id, object_type, principal_type, role_identifier, resource_group_identifier, include_parent_scopes, identifiers, sort_orders, page_token, has_module, module_type, only_favorites, identifier_filter, exclude_rego, include_policy_set_count, entity, created_date_from, created_date_to, include_child_scopes, freeze_status, service_id, target_id, dataset_id, metric_set_id, run_id, eval_id, set_id, suite_id, trace_id, label, annotator_type, tag, provider, activity_id, kinds, annotations, object_kind, severity, impacted_service, environment, commander, text, reported_after, reported_before, sort_direction, service, deployed_after, deployed_before. Call harness_describe for filters available on a specific resource_type.
project_idNoProject identifier (overrides default)
search_termNoFilter results by name or keyword
resource_typeNoResource type to list. Auto-detected from url.
resource_scopeNoScope to query. Use account for account-level resources and to omit org/project defaults; org injects only org; project injects org+project. Auto-detected from url.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoCurrent page number (0-indexed) when provided by the API
itemsNoArray of resource objects or primitive values when the API returns a canonical list
totalNoTotal number of matching resources when provided by the API
Behavior4/5

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

Annotations already mark it as read-only. The description adds transparency by explaining the URL auto-extraction feature and the need to call harness_describe for filter/param details. This goes beyond annotations without contradicting them.

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 sentences cover the core purpose and key feature (URL auto-extraction). The description is front-loaded with the primary action and avoids unnecessary details, making it efficient for an agent to parse.

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 complexity (11 parameters, extensive filters, output schema exists), the description captures the essentials. It omits details like compact mode and nested resources, but the rich schema and annotations compensate. Slightly more context would improve completeness.

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?

With 100% schema description coverage, the baseline is 3. The description adds value by explaining how the 'url' parameter auto-extracts scope and by referencing harness_describe for resource-specific fields and filters, providing context beyond the schema entries.

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 clearly states 'List Harness resources with filtering and pagination', identifying a specific verb and resource. This distinguishes it from siblings like harness_get (single resource) and harness_search (broader search) by highlighting pagination and filtering capabilities.

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 usage through features like filtering and pagination, but does not explicitly state when to use this tool versus alternatives like harness_search or harness_get. It cross-references harness_describe for additional context, which is helpful but not sufficient for clear guidance.

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