[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Create a broadcast round

> Add a round to a broadcast, fed from a PGN URL, Lichess game IDs or Lichess usernames. Input schema, a tools/call example and an example result.

Source: https://cotlet.dev/docs/mcp/lichess/create_broadcast_round

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

Add a round to a broadcast, fed from a PGN URL, Lichess game IDs or Lichess usernames.

Lichess MCP tools: https://cotlet.dev/docs/mcp/lichess.md

MCP tool: `lichess_write → create_broadcast_round`

Access: write. Confirm: waits for the user's OK before it runs.

Creates the round and returns its ID and URL. The round must have one source type; with none, it can only be fed by pushing PGN. The round appears on the broadcast page for everyone who can view the broadcast. By default you confirm each call; you can switch that off for this tool.

## Parameters

| Name | Type | Required | Description |
|---|---|---|---|
| `broadcast_id` | string | yes | Broadcast ID from list_broadcasts or create_broadcast. |
| `name` | string | yes | Round name, e.g. Round 1. |
| `source` | string | yes | single_pgn_url, multiple_pgn_urls, lichess_game_ids or lichess_usernames. Use exactly one. |
| `pgn_urls` | string[] | no | PGN URL, or several, for the two PGN sources. |
| `game_ids` | string[] | no | Lichess game IDs for lichess_game_ids. |
| `usernames` | string[] | no | Lichess usernames for lichess_usernames. |
| `starts_at` | string | no | ISO start time. Read in the time zone set on the broadcast. |

## tools/call

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "lichess_write",
    "arguments": {
      "operation": "create_broadcast_round",
      "arguments": {
        "broadcast_id": "broadcast_8c41d2",
        "name": "Jane Doe",
        "source": "source"
      }
    }
  }
}
```

## Example response

```json
{
  "content": [
    {
      "type": "text",
      "text": "{ ... same JSON as structuredContent ... }"
    }
  ],
  "structuredContent": {
    "round_id": "Kf3nQ8vD",
    "broadcast_id": "Zp4tNc6h",
    "name": "Round 1",
    "source": "single_pgn_url",
    "starts_at": "2026-10-24T10:00:00Z",
    "url": "https://lichess.org/broadcast/riverside-chess-club-championship-2026/round-1/Kf3nQ8vD"
  },
  "isError": false
}
```

Previous: [Create a broadcast tournament](https://cotlet.dev/docs/mcp/lichess/create_broadcast.md)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.