Skip to main content
Glama

harness_list

Read-only

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

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
resource_typeNoResource type to list. Auto-detected from url.
urlNoHarness UI URL — auto-extracts org, project, and type
org_idNoOrganization identifier (overrides default)
project_idNoProject identifier (overrides default)
pageNoPage number, 0-indexed
sizeNoPage size (1–100)
search_termNoFilter results by name or keyword
compactNoStrip verbose metadata from list items, keeping only essential fields (default true)
paramsNoAdditional identifiers for nested resources (e.g. repo_id for pull requests). Call harness_describe for fields per resource_type.
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, environment_id, deployment_type, secret_identifier, secret_name, secret_manager_identifiers, 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, folder_id, reporting_timeframe, kind, namespace, entity_identifier, scope_level, state, after, before, offset, workspace_id, rollout_status_id, repo_creds_id, agent_id, app_name, pod_name, container, tail_lines, resource_name, group, version, scope, experiment_run_ids, notify_ids, hub_identity, infrastructure_type, infrastructure, include_all_scope, sort_field, sort_ascending, experiment_id, include_legacy_infra, is_enterprise, permissions_required, infra_type, entity_type, only_templatised_faults, environment_type, sort_type, sort_order, cloud_filter, group_by, time_filter, limit, time_resolution, min_saving, perspective_id, min_amount, min_anomalous_spend, field_id, field_identifier, aspect, cloud_account_id, start_date, end_date, team_ref_id, date_start, date_end, feature_type, granularity, metric, integration_type, profile_id, metric_type, artifact_type, source_id, artifact_id, dependency_type, purl, standards, target_version, severity_codes, issue_types, target_ids, target_types, pipeline_ids, scan_tools, exemption_statuses, principal_type, role_identifier, resource_group_identifier, include_parent_scopes, has_module, module_type, identifier_filter, exclude_rego, include_policy_set_count, entity, created_date_from, created_date_to, include_child_scopes, freeze_status, service_id. Call harness_describe for filters available on a specific resource_type.
include_visualNoInclude an inline PNG chart of the results (default false). Supported for execution resource_type. Use when user asks for a visualization, chart, or graph.
visual_typeNoChart type when include_visual=true. 'timeseries' = daily execution counts, 'pie' = breakdown by status, 'bar' = breakdown by pipeline. Default 'pie'.pie
Behavior4/5

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

The description adds valuable behavioral context beyond annotations: URL auto-extraction and filtering/pagination. With readOnlyHint=true, it correctly indicates no side effects. It discloses important traits but could mention rate limits or permission requirements.

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 extremely concise with two sentences covering the core functionality and a key behavioral trait (URL auto-extraction). Every word earns its place; no redundancy.

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

Completeness3/5

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

Given the complexity (12 parameters, nested objects, many siblings) and no output schema, the description is adequate but not thorough. It lacks explanation of the params and filters objects, or how URL extraction interacts with other parameters. Schema covers details, but the tool description could provide more high-level context.

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 tool description adds minimal value for parameter semantics. The schema already documents each parameter well, including the URL auto-detection hint. Baseline 3 is appropriate.

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', specifying the verb (list), the resource (Harness resources), and key features (filtering, pagination, URL auto-extraction). It distinguishes from sibling tools like harness_get (single resource) and harness_search (different search behavior).

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 for listing multiple resources but does not explicitly state when to use this tool versus alternatives like harness_get or harness_search. No when-not-to or exclusion criteria are provided, leaving some ambiguity.

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

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