Build a content template
build_content_templateBuilds a keyword's content template, from its top 10 Google results: the typical length of the pages (the middle half of their word counts, a fact and not a target: Google sets no word count), the median number of subheadings and the median readability (0 hard to 100 easy), which help readers and are not Google ranking factors, the terms most of the pages use, each in all its forms, with how many use each, and each page with its headings, or why it could not be read. Length and terms are compared only when at least 5 pages could be read. Estimated price per keyword: up to $0.02, for the SERP analysis, when none of the last 12 hours is saved, then each page with no saved copy. A template whose results are still current is answered from what is saved at no charge, and every build opens free on the Content Template page. Pages that could not be bought are listed, and the next call buys only them. When Google hid the address of every top result on desktop, the mobile results are bought once more, charged on top of that estimate but never above the call's maximum, and the template says it came from mobile. When Google hid the address of some results, the template is built from the others (at least 3 must be readable) and names the ones it could not read; with fewer, no template is built and the answer says what the search results were charged. Each call may spend up to the workspace's agent spend limit ($2.00 unless changed in Settings) without asking: it holds at most its estimate plus a margin while it runs and is charged what it bought, never more. A call whose maximum is above the limit is refused before anything is bought, with its estimate and maximum: ask the user, then call again with approvedMaxCostUsd set to the amount they approved.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"projectId": "<projectId>",
"keyword": "<keyword>"
},
"name": "build_content_template"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mobile | No | Build from Google's mobile results instead of the desktop ones. Use it only after a build said too few top results could be read on desktop and that mobile was not tried: it is priced and held as a new build. | |
| keyword | Yes | The keyword a page should rank for, such as 'espresso machine'. | |
| projectId | Yes | Required. The Visibility Genies project this call works in and is billed to. Call list_projects to find one. | |
| languageCode | No | Language code such as en, es or vi. When left out, the language of the project's default market is used (see list_projects). | |
| locationCode | No | Market location code, for example 2840 for the United States. When left out, the project's default market is used (shown by list_projects and changed in project settings). A few countries, Iceland (2352) among them, only have Google Ads data: search volume, CPC and trends are available there, but keyword difficulty, search intent and domain analytics are not. | |
| approvedMaxCostUsd | No | The most, in USD, the user approved for this call after seeing its estimate and maximum. Only needed after a call was refused for costing more than the workspace's agent spend limit; never set it without asking the user. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cost | No | ||
| meta | No | ||
| bought | Yes | ||
| savedAt | Yes | ||
| template | Yes | ||
| templates | Yes | ||
| savedResultId | No |