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

# MCP tools: grow

> Grow tools of the Summer Engine MCP. See how your published game is doing. For each tool: what it does, what it needs, inputs, output and an example.

See how your published game is doing. 2 tools. What each column means, and how to connect: [MCP tools reference](/mcp/tools-reference).

<Note>
  Generated from the tools' own definitions: the `summer-engine` npm package `3.3.0` (its MCP server's `tools/list`, `library/tools/*/resource.yaml` and `registry/generated/index.json` in [SummerEngine/summer](https://github.com/SummerEngine/summer)) and the hosted Summer Engine MCP (`src/lib/mcp/hosted` at commit `8c4351ee30`). If something here is wrong, the tool definition is wrong.
</Note>

| Tool | Needs | What it does |
| - | - | - |
| [`summer_grow_analytics`](#summer_grow_analytics) | Summer account | One game's analytics on Summer Games for the last 7, 28 or 90 days (UTC): totals (store page views, launches, play sessions, play time, average session), every day of the window, and the game's top custom events (sent… |
| [`summer_grow_overview`](#summer_grow_overview) | Summer account | Summer Grow across the signed-in owner's games on Summer Games: store page views, launches, play sessions and play time per game and in total, for the last 7, 28 or 90 days (UTC). |

### summer\_grow\_analytics

On the hosted MCP.

One game's analytics on Summer Games for the last 7, 28 or 90 days (UTC): totals (store page views, launches, play sessions, play time, average session), every day of the window, and the game's top custom events (sent with Summer.client.analytics.capture; counts are approximate). Real data; read-only. gameId comes from [`summer_store_list_games`](/mcp/tools/publish#summer_store_list_games).

| | |
| - | - |
| **Needs** | Your Summer account (OAuth). In the npm MCP: `summer login --store` |
| **Hints** | `readOnlyHint` |

**Inputs:**

| Input | Type | Required | Description |
| - | - | - | - |
| `gameId` | string | Yes | |
| `days` | 7 \| 28 \| 90 | No | Window in whole UTC days, today included: 7, 28 or 90. Default `7`. |

<Accordion title="Input JSON schema">
  ```json theme={null}
  {
    "type": "object",
    "properties": {
      "gameId": {
        "type": "string",
        "pattern": "^[A-Za-z0-9_-]{1,128}$"
      },
      "days": {
        "description": "Window in whole UTC days, today included: 7, 28 or 90.",
        "default": 7,
        "anyOf": [
          {
            "type": "number",
            "const": 7
          },
          {
            "type": "number",
            "const": 28
          },
          {
            "type": "number",
            "const": 90
          }
        ]
      }
    },
    "required": [
      "gameId"
    ]
  }
  ```
</Accordion>

**Output:** MCP text content holding JSON; errors set `isError`.

```json Example call theme={null}
{
  "name": "summer_grow_analytics",
  "arguments": {
    "gameId": "<gameId>"
  }
}
```

***

### summer\_grow\_overview

On the hosted MCP.

Summer Grow across the signed-in owner's games on Summer Games: store page views, launches, play sessions and play time per game and in total, for the last 7, 28 or 90 days (UTC). Real data from Summer Games; read-only. For one game's daily numbers and custom events use [`summer_grow_analytics`](/mcp/tools/grow#summer_grow_analytics).

| | |
| - | - |
| **Needs** | Your Summer account (OAuth). In the npm MCP: `summer login --store` |
| **Hints** | `readOnlyHint` |

**Inputs:**

| Input | Type | Required | Description |
| - | - | - | - |
| `days` | 7 \| 28 \| 90 | No | Window in whole UTC days, today included: 7, 28 or 90. Default `7`. |

<Accordion title="Input JSON schema">
  ```json theme={null}
  {
    "type": "object",
    "properties": {
      "days": {
        "description": "Window in whole UTC days, today included: 7, 28 or 90.",
        "default": 7,
        "anyOf": [
          {
            "type": "number",
            "const": 7
          },
          {
            "type": "number",
            "const": 28
          },
          {
            "type": "number",
            "const": 90
          }
        ]
      }
    }
  }
  ```
</Accordion>

**Output:** MCP text content holding JSON; errors set `isError`.

```json Example call theme={null}
{
  "name": "summer_grow_overview",
  "arguments": {}
}
```

***


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