---
title: "Read body schema"
description: "Answers what a save takes for a kind of body: its block types, each block's props with their types, values and limits, which are required, and where blocks may sit."
---

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

# Read body schema

Needs the file:read scope.

## Call

- Tool: `get_body_schema`
- Scope: `file:read`
- Reads only.
- Acts on a store.

## Arguments

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `store` | `string` | No | The store to act on. |
| `kind` | `"product" or "store" or "event" or "all" or "page" or "portfolio" or "lesson" or "article"` | Yes | The kind of body: `store`, `page`, `product` (any product but an event or a portfolio), `event`, `portfolio`, `lesson` (an entry of any product but a blog or a podcast, a portfolio's posts included), `article` (a blog's or a podcast's entry) or `all`. |

```json
{
  "type": "object",
  "properties": {
    "store": {
      "type": "string",
      "description": "The store to act on."
    },
    "kind": {
      "description": "The kind of body: `store`, `page`, `product` (any product but an event or a portfolio), `event`, `portfolio`, `lesson` (an entry of any product but a blog or a podcast, a portfolio's posts included), `article` (a blog's or a podcast's entry) or `all`.",
      "type": "string",
      "enum": [
        "product",
        "store",
        "event",
        "all",
        "page",
        "portfolio",
        "lesson",
        "article"
      ]
    }
  },
  "required": [
    "kind"
  ],
  "additionalProperties": false
}
```

## Answer

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `kinds` | `array of object` | Yes |  |
| `blocks` | `array of object` | Yes | Every type a listed kind takes, in its body or its texts. |

The answer's full shape is on [its API reference page](/merchant-api/reference/get-body-schema).

## Errors

A refused call is a tool error. Its `structuredContent` holds a `code` and its `context`, except for `client-fault`. This tool may answer:

- `invalid`: an argument is malformed; `context.path` names it.
- `invalid` at `["store"]`: `store` is missing while the connection reaches more than one store, or names a store it doesn't reach.
- `not_permitted`: this connection may not make this call. When `context.reason` is `limit`, too many calls: `retry_after` says when to try again.
- `internal` or `unavailable`: the call failed inside Sherpo. A read marked `transient` may be retried.
- `client-fault`: the server failed around the call. `reached_core` says whether it reached Sherpo; the call may be made again.
- HTTP 403 with `insufficient_scope`: the connection lacks the scope this tool needs.
- HTTP 401 with `invalid_token`: the access token expired or the connection ended. Refresh the token, and connect again if the refresh fails or the new token is refused too.

Any other code may come back too, such as a `conflict` when the state changed under the call. When the answer was already streaming, a 401 or 403 comes back as a tool error with only its text. See [Errors](/merchant-mcp/errors) for every code and its context.

Source: https://docs.sherpo.io/merchant-mcp/tools/get_body_schema/index.mdx
