Read technical page features

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.

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

{
  "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 explains estimates and empty results; errors and recovery covers invalid requests and temporary failures. HTTP equivalent: Read technical page features. HTTP parameters and defaults can differ.

Get started

Connect securely

Read measurements

Build dependable integrations

Build reports

Report recipes

Reference

Session and discovery

Visibility measurements

Sources and evidence

Changes and trends

Google data

Pages and report planning

HTTP operations

Read technical page features

Parameters

Example call

Read the response

Fields to use

Response example

Important behavior

​Parameters

​Example call

​Read the response

​Fields to use

​Response example

​Important behavior

Parameters

Example call

Read the response

Fields to use

Response example

Important behavior