Capable

Share a call recording

share_recording

Share one recorded call outside the workspace through a private, expiring link to a page that plays it and, unless include_transcript is false, its transcript. create (default): emails each recipient their own link as "{you} via Capable" (replies reach you), or with no recipients returns one link to send yourself; a link is shown once. Needs confirm:true — without it, a preview and nothing sent. list: the links with status and plays, plus the call's outside attendees as suggested_recipients. revoke: turn one link off by share_id.

When to use: When someone outside the workspace asks for a call's recording — email them a private, expiring link, or get one to send yourself; list or revoke links later.

Example: Send Anna the recording of yesterday's call with Acme.

Input Schema

Name	Required	Description
`action`	No	create (default), list or revoke.
`confirm`	No	create: true sends; otherwise a preview.
`message`	No	create: a short note above the link in the email.
`share_id`	No	revoke: the link's id.
`recipients`	No	create: up to 10 addresses, one link each; omit for a link to copy.
`recording_id`	Yes	The recording's id (from get_context on the meeting touch). A uuid.
`expires_in_days`	No	create: days the link works (default 14).
`include_transcript`	No	create: false shares the video only (default true).

Output Schema

Name	Required	Description	Default
`note`	No
`share`	No
`action`	No
`shares`	No
`applied`	No
`created`	No
`recording`	No
`email_available`	No
`requires_confirm`	No
`suggested_recipients`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 24, 2026

removedInput schema / properties / confirm / anyOf

Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]

addedInput schema / properties / confirm / type

Added value: +[
+  "boolean",
+  "string",
+  "number"
+]

removedInput schema / properties / expires_in_days / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "string"
-  }
-]

addedInput schema / properties / expires_in_days / type
```
Added value: +[
+  "number",
+  "string"
+]
```

removedInput schema / properties / include_transcript / anyOf

Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]

addedInput schema / properties / include_transcript / type

Added value: +[
+  "boolean",
+  "string",
+  "number"
+]

Changed1 schema field changedOct 20, 2026
- removedInput schema / $schema
```
Removed value: -"https://json-schema.org/draft/2020-12/schema"
```
Changed10 schema fields changedOct 19, 2026
- removedOutput schema / $schema
```
Removed value: -"https://json-schema.org/draft/2020-12/schema"
```
- removedOutput schema / additionalProperties
```
Removed value: -{}
```
- removedOutput schema / properties / created / items / additionalProperties
```
Removed value: -{}
```
- removedOutput schema / properties / created / items / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / recording / additionalProperties
```
Removed value: -{}
```
- removedOutput schema / properties / recording / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / share / additionalProperties
```
Removed value: -{}
```
- removedOutput schema / properties / share / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / shares / items / additionalProperties
```
Removed value: -{}
```
- removedOutput schema / properties / shares / items / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```
AddedOct 8, 2026

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the annotations by disclosing the confirm:true gate and preview behavior, that links are shown once and expire, that each recipient gets their own email sent as '{you} via Capable', the 10-recipient cap, default expiry, and transcript inclusion. These are exactly the side effects an agent needs before triggering an outbound, open-world action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and every sentence carries information (modes, gating, defaults, example). The first paragraph is dense and runs long, but little of it is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, yet the description still summarizes what the list action returns (status, plays, suggested_recipients) and explains how to obtain recording_id via get_context. Nothing an agent needs to invoke this correctly across all three actions is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3; the description nevertheless adds cross-parameter meaning, e.g. that omitting recipients returns a self-send link and that confirm governs send-vs-preview. Defaults (14 days, transcript true) largely restate the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Share one recorded call outside the workspace') plus the mechanism (private, expiring link). It also enumerates the three actions (create/list/revoke) so the agent can distinguish the modes without inspecting the schema, and it is clearly distinct from siblings like record_meeting or stop_recording.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The explicit 'When to use' section plus a concrete example ('Send Anna the recording of yesterday's call with Acme') give a clear trigger condition. It also describes when each action applies ('list or revoke links later'), though it does not name a sibling tool or a when-not-to-use case.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Capable tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?