> For the complete documentation index, see [llms.txt](https://docs.rad.live/rad/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rad.live/rad/rad-tv-developer-api/engagement.md).

# Engagement

The API supports likes, comments, and channel follow/unfollow. Catalog types (Feature, Episode, Stream, etc.) and Content implement like and comment interfaces.

## Likes

### Likeable entities

Content and catalog types (Feature, Episode, Stream, Serie, Season, Miniseries) implement **Likeable**: they have `id` (DID) and `likes: ContentLikes`. `ContentLikes` has:

* **count** — Total like count
* **isLiked** — Whether the current authenticated user has liked the entity

{% hint style="info" %}
`likes` is never null; when unauthenticated or on error, `count` is `0` and `isLiked` is `false`.
{% endhint %}

### Like / unlike (by DID)

GraphQL:

```graphql
mutation {
  likeContent(id: "did:rad.live:content/feature/abc123") {
    id
    likes { count isLiked }
  }
}

mutation {
  unlikeContent(id: "did:rad.live:content/feature/abc123") {
    id
    likes { count isLiked }
  }
}
```

MCP: `like_content`, `unlike_content` with `id` (content DID).

{% hint style="info" %}
Both mutations are idempotent: calling `likeContent` multiple times does not change the result; calling `unlikeContent` on unliked content has no effect.
{% endhint %}

## Comments

### Listing comments

GraphQL: `comments(contentId: DID!, limit: Int, start: Int)`\
MCP: `list_comments` with `contentId`, optional `limit`, `start`.

Commentable entities (Content and catalog types) also expose `comments(limit, start)` on the type itself.

### Creating a comment

GraphQL:

```graphql
mutation {
  createComment(
    contentId: "did:rad.live:content/feature:xyz"
    body: "Great video!"
  ) {
    id
    body
    contentId
    createdAt
    author { id username }
  }
}
```

MCP: `create_comment` with `contentId` and `body`.

The authenticated user is set as the comment author. Comments are stored and queried via the User API (12core).

## Channel follow / unfollow

### Follow / unfollow

GraphQL:

```graphql
mutation {
  followChannel(channel: "did:rad.live:channel/<uuid>") { ok }
}

mutation {
  unfollowChannel(channel: "did:rad.live:channel/<uuid>") { ok }
}
```

MCP: `follow_channel`, `unfollow_channel` with `channel` (channel DID).

{% hint style="info" %}
Follow/unfollow are idempotent. Channels expose `followersCount` and `isFollowed` (whether the current user follows).
{% endhint %}

### Followed channels

GraphQL: `me.followedChannels`\
MCP: `list_followed_channels` (no arguments).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.rad.live/rad/rad-tv-developer-api/engagement.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.