> 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/mcp/resources-and-prompts.md).

# Resources and Prompts

## Resource: rad://api/capabilities

The MCP server exposes one resource: **`rad://api/capabilities`**.

Contents (JSON):

* `name` — Server name (e.g. `radtv-api`)
* `version` — Server version (e.g. `2025-06-18`)
* `tools` — Array of tool names (all 23 tools)
* `llms_txt` — Path to the llms.txt manifest (e.g. `/llms.txt`)
* `graphql` — Path to the GraphQL endpoint (e.g. `/graphql`)
* `description` — Short description of the API

Use this resource to discover what the server supports without calling `tools/list`. MIME type: `application/json`.

***

## Prompts

Prompts are predefined message templates that guide the agent through a workflow.

### create\_content\_and\_upload

Description: Guide to create content, create content asset, then upload file via TUS.

Summary:

{% stepper %}
{% step %}

### Create content

Call `create_content` with title/summary/type.
{% endstep %}

{% step %}

### Create content asset

Call `create_content_asset` with the returned content id, filename, and size.
{% endstep %}

{% step %}

### Upload file

POST the file to the returned endpoint with the header `Authorization: Bearer <api-key>` and `Content-Type: multipart/form-data`.
{% endstep %}
{% endstepper %}

***

### follow\_a\_channel

Description: Guide to follow a channel by DID.

Summary:

Use the `follow_channel` tool with the channel DID (e.g. `did:rad.live:channel/<uuid>`). Get channel DIDs from `list_followed_channels` or from the API.

***

## llms.txt

The full manifest for LLMs and agents is available at:

* `GET /llms.txt`
* `GET /.well-known/llms.txt` (redirects to `/llms.txt`)

It includes authentication instructions, the MCP tool list with arguments, GraphQL summary, and links to the GraphQL and MCP endpoints. Use it when your client supports llms.txt discovery.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rad.live/rad/rad-tv-developer-api/mcp/resources-and-prompts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.