---
title: "list_search_terms. Metadata MCP tool reference"
url: https://metadata.io/developers/tools/list_search_terms
description: "Review the Google Ads search terms report with filtering, sorting, and pagination. Read tool on the Metadata MCP server, with its full JSON Schema and a real recorded response."
source: metadata.io
---

# list_search_terms

Review the Google Ads search terms report with filtering, sorting, and pagination.

Read [search](https://metadata.io/developers/tools/#cat-search)

## What it does

## Arguments

| Argument | Type |   | Notes |
|---|---|---|---|
| `searchTerm` | string |   | Optional substring filter on the search term text. |
| `experiment` | string |   | Optional experiment name substring filter. |
| `keyword` | string |   | Optional matched-keyword substring filter. |
| `matchType` | array |   | Optional subset of match types to include. |
| `startDate` | string |   | Optional ISO-8601 timestamp lower bound (e.g. 2026-06-01T00:00:00.000Z). |
| `endDate` | string |   | Optional ISO-8601 timestamp upper bound (e.g. 2026-06-30T23:59:59.999Z). |
| `page` | integer |   | 0-based page index. Default 0. |
| `size` | integer |   | Rows per page. Default 12 (kept small to limit chat-context tokens), max 100. |
| `sort` | string |   | Sort criteria in format '<field>,<direction>'. Default 'clicks,desc'. Sortable fields: searchTerm, matchType, experiment, addedExcluded, keyword, impressions, clicks, ctr, averageCpc, spent, conversions, costPerConversion. |
| `channel` | string |   | Ad channel scope. Both search channels are supported. These are PER-CHANNEL resources: GOOGLE_ADS and MICROSOFT_ADS hold separate sets, and one is invisible to the other. Defaults to GOOGLE_ADS when the user does not say which.one of: `GOOGLE_ADS`, `MICROSOFT_ADS` |

## Request

**Request template, not a complete runnable example.** Replace placeholders, empty objects, arrays, and zero values with valid account-specific inputs. Read required fields and nested constraints in the full schema. Confirm the account, connected channels, and referenced assets before calling a write tool.

## Response

Real, from the production server, in **2164 ms**. The full response was 6,620 bytes; this is the first part of it. Values that identify a customer or disclose money are replaced with typed placeholders; keys, types and nesting are exactly as returned.

## Related

Other search tools:

- [add_keywords_to_negative_lists](https://metadata.io/developers/tools/add_keywords_to_negative_lists) Writes
- [add_negative_keyword_lists_to_live_campaigns](https://metadata.io/developers/tools/add_negative_keyword_lists_to_live_campaigns) Writes
- [create_keywords](https://metadata.io/developers/tools/create_keywords) Writes
- [create_negative_keywords_list](https://metadata.io/developers/tools/create_negative_keywords_list) Writes
- [delete_negative_keyword_lists](https://metadata.io/developers/tools/delete_negative_keyword_lists) Destructive
- [duplicate_negative_keywords_list](https://metadata.io/developers/tools/duplicate_negative_keywords_list) Writes
- [experiments_keywords_stats](https://metadata.io/developers/tools/experiments_keywords_stats) Read
- [get_negative_keywords_list_details](https://metadata.io/developers/tools/get_negative_keywords_list_details) Read

[Browse the tool catalog](https://metadata.io/developers/tools/) · [machine-readable index](https://metadata.io/developers/tools.json)