> ## Documentation Index
> Fetch the complete documentation index at: https://docs.iqrush.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Read technical page features

> Retrieve recorded features for a page in the selected measurement.

Retrieve recorded features for a page in the selected measurement.

**MCP tool:** `get_technical_features`. **Operation:** read. Uses the authorized connection; no project or content changes are made by this tool.

## Parameters

| Name | Type | Required | Default | Meaning and accepted values |
| - | - | - | - | - |
| `project_id` | string | Yes | `Required` | Project ID from list\_projects. Select the project in the intended workspace and environment. |
| `run_id` | string | Yes | `Required` | Run ID from list\_runs for this project. Use the exact returned value and check readiness before reading measurements. |
| `url` | string | Yes | `Required` | Page URL or domain to inspect among this run’s captured pages. Verify matched\_url before attributing the features to a page. |
| `feature_group` | string | No | `''` | Case-insensitive substring filter on feature\_key in this edition; it does not select the nullable feature\_group response field. |
| `feature_domain` | string | No | `''` | Not applied by the current technical-features HTTP route. Omit in this edition. |

## Example call

Replace ID placeholders and example selections with values from your account. This is the `params` object for MCP `tools/call`.

```json theme={null}
{
  "name": "get_technical_features",
  "arguments": {
    "project_id": "PROJECT_ID",
    "run_id": "RUN_ID",
    "url": "https://www.colorescience.com/collections/mineral-sunscreens"
  }
}
```

## Read the response

Read `data.matched_url`, `features`, and any `url_segments`. Feature rows include `feature_key`, `value`, nullable score/group fields, and `run_spread` when available.

### Fields to use

These selected fields explain the example and the result to preserve. Field presence depends on the response; this is not a complete response schema.

| Field | Meaning and use |
| - | - |
| `data.url_queried` | URL or domain submitted by the caller. |
| `data.matched_url` | Captured page actually matched. Confirm this before attributing its features to a requested URL. |
| `data.n_features` | Number of feature rows returned after the optional filter. |
| `data.features[].feature_key` | Feature identifier supplied by the captured page record. |
| `data.features[].value` | Observed feature value; its meaning depends on feature\_key. It is not automatically a quality score. |
| `data.features[].normalized_score` | Unpopulated in this edition. Do not treat null as a zero score. |
| `data.features[].feature_group` | Unpopulated in this edition; the request’s feature\_group filter searches feature\_key instead. |

## Response example

Selected fields from an observed IQRush Dev response. Lists are shortened and project/run IDs are placeholders. Omitted fields remain available in the actual response.

```json theme={null}
{
  "data_ready": true,
  "data": {
    "url_queried": "https://www.colorescience.com/collections/mineral-sunscreens",
    "matched_url": "https://www.colorescience.com/collections/mineral-sunscreens",
    "n_features": 16,
    "features": [
      {
        "feature_key": "titleTag",
        "display_name": "titleTag",
        "value": 1,
        "normalized_score": null,
        "feature_group": null,
        "feature_domain": null
      }
    ]
  }
}
```

Read the actual returned scope, counts, and interval levels before interpreting these fields.

## Important behavior

These are observed features, not proven optimization targets. `feature_group` matches feature-key text. `feature_domain` is not applied by the HTTP route in this edition.

Check tool and payload errors before using the result. [Response handling](/developers/guides/09-responses-and-metrics) explains estimates and empty results; [errors and recovery](/developers/guides/13-errors) covers invalid requests and temporary failures.

HTTP equivalent: [Read technical page features](/developers/http/http-get-technical-features). HTTP parameters and defaults can differ.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.