Get Recording Usage
get_recording_usageRead-onlyIdempotent
Report how much footage a Cloud Recording actually holds: seconds recorded against the capacity of its queue, when the queue started, and the configured retention. recorded_seconds says whether footage exists and how near the limit it is. queue_started_at is when Angelcam started the queue; it can be far older than the retention (a camera that went offline long ago still shows its old date), so never read it as the oldest footage that still exists. To see how far back footage really reaches, use get_recording_timeline. Takes the recording_id from list_recordings, not a camera_id.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"recording_id": "<recording_id>",
"session_id": "<session_id>"
},
"name": "get_recording_usage"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| space_id | No | Angelcam space. Call list_spaces; if there is more than one, ask the user which and pass its id - never guess or assume the active one. Reuse it on every later call; omit only with a single space. | |
| session_id | Yes | Session continuity handle, one of two values: the ses_ ID issued for the task underway, or start. This server cannot link your calls between requests on its own, so session continuity travels in this parameter instead. If you were handed a session_id for this task — for example by the agent that spawned you — send that exact value from your first call. Otherwise send start on your first call; the server will issue an opaque correlation ID in the mcp_session field of the result, or in a text block at the start of the result beginning [session_id issued. Then send that exact ses_ value on every later call and hand it to any subagents working the same task. start always begins a new, unrelated task — never send it mid-task. If you send a value this server does not recognize, the result reports it: mcp_session.status of unrecognized, or a text block beginning [session_id unrecognized; re-send the ID issued for this task, or start if none was issued yet. Never invent a ses_ value. | |
| recording_id | Yes |