Needs the file:read scope.
Call
- Tool:
get_media_output - Scope:
file:read - Reads only.
- Acts on a store.
Arguments
| Name | Type | Required | Description |
|---|---|---|---|
store |
string |
No | The store to act on. |
asset |
object |
Yes | |
kind |
"summary" or "chapters" or "transcript" or "subtitles" |
Yes |
{
"type": "object",
"properties": {
"store": {
"type": "string",
"description": "The store to act on."
},
"asset": {
"type": "object",
"properties": {
"id": {
"type": "string",
"minLength": 1,
"maxLength": 512
}
},
"required": [
"id"
],
"additionalProperties": false
},
"kind": {
"type": "string",
"enum": [
"summary",
"chapters",
"transcript",
"subtitles"
]
}
},
"required": [
"asset",
"kind"
],
"additionalProperties": false
}Answer
| Name | Type | Required | Description |
|---|---|---|---|
content |
object or null |
Yes | |
unreadable |
boolean |
Yes | Whether the stored content is not what an edit may save, so content is null though has_content holds. |
truncated |
boolean |
Yes | Whether content holds less than the stored subtitles (cues left out or texts cut), so saving it drops the rest. |
kind |
string |
Yes | |
asset_id |
string |
Yes | |
status |
string |
Yes | |
has_content |
boolean |
Yes | Whether content landed, which a run still generating or one that failed may keep from before. |
revision |
number |
Yes | The file’s revision the content came from, or the running generation reads. |
language |
string or null |
Yes | |
reason |
string or null |
Yes | |
bytes |
number or null |
Yes | The output’s size in bytes; null when it is charged nothing. |
deadline |
string or null |
Yes | |
updated_at |
string or null |
Yes | |
published_at |
string or null |
Yes | |
created_at |
string or null |
Yes |
The answer’s full shape is on its API reference page.
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.pathnames it.invalidat["store"]:storeis missing while the connection reaches more than one store, or names a store it doesn’t reach.not_found: nothing matches a reference given.not_permitted: this connection may not make this call. Whencontext.reasonislimit, too many calls:retry_aftersays when to try again.internalorunavailable: the call failed inside Sherpo. A read markedtransientmay be retried.client-fault: the server failed around the call.reached_coresays 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 for every code and its context.