get_growth compares two dates on one keyword series and returns a percent. The window is selected with percent_growth, an array of preset strings. Each preset is a two-date comparison, not a rolling average. Default if the field is omitted: ["12M"]. The call is POST https://api.trendsapi.ai/api with source and keyword. Parse the string body before reading results. Mode notes sit on the API reference. What the underlying 0-100 values mean sits on the score page.
The preset strings
These values are valid percent_growth items on the Trends API MCP server in this session.
| Preset | Kind |
|---|---|
7D |
Days |
1W |
Weeks |
14D |
Days |
2W |
Weeks |
30D |
Days |
1M |
Months |
2M |
Months |
3M |
Months |
6M |
Months |
9M |
Months |
12M |
Months |
1Y |
Years |
18M |
Months |
24M |
Months |
2Y |
Years |
36M |
Months |
3Y |
Years |
48M |
Months |
4Y |
Years |
60M |
Months |
5Y |
Years |
MTD |
Calendar, month to date |
QTD |
Calendar, quarter to date |
YTD |
Calendar, year to date |
Copy the cell. 12M is not 12m. YTD is not ytd.
POST https://api.trendsapi.ai/api
Authorization: Bearer <api_key>
Content-Type: application/json
{"mode":"get_growth","source":"google search","keyword":"bitcoin","percent_growth":["3M","12M","YTD"]}
source may be a comma-separated list. get_time_series still takes exactly one source and does not take percent_growth.
What one result row contains
After the second parse, results is one object per window.
| Field | Meaning |
|---|---|
period |
The preset or custom name |
growth |
Percent change, signed |
direction |
Increase or decrease |
recent_date |
The later date |
baseline_date |
The earlier date |
recent_value |
0-100 at recent_date |
baseline_value |
0-100 at baseline_date |
growth is not a 0-100 score. Absolute counts, when present, are a different field documented on volume vs score.
Custom date pairs on REST
The official REST docs accept an object in percent_growth:
{"name": "Last Year", "recent": "2025-12-31", "baseline": "2024-12-31"}
recent is the later date. baseline is the comparison date. Both are YYYY-MM-DD. The MCP tool in this session does not list that object shape. Use REST when the window is a launch date or a fiscal year that is not a preset.
One request, several windows
Passing ["3M","12M","YTD"] is still one POST. Caps and plan names stay on pricing. Source spelling rules sit on keyword formats.