Skip to main content
Glama
speakai

Speak AI MCP Server

Official
by speakai

Create Recorder

create_recorder

Set up a recorder or survey to collect audio and video submissions with configurable options for duration, notifications, and respondent information.

Instructions

Create a new recorder or survey for collecting audio/video submissions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
metaNoBranding/customization: { primaryColor, backgroundImg, logo, fontColor, fontFamily, theme, customCSS, hideWaveform, hideTitle, hideDescription, hideSubmitButton, submitButtonLabel, countdown, hideImages }
nameYesDisplay name for the recorder
optionsNoCapture options: { audio, video, screenShare, liveTranscription, upload:{ file, text, multiple, url } } — all booleans
durationNoRecording duration: { minDuration, maxDuration } in seconds
folderIdNoFolder to store recordings in
descriptionNoRecorder description
notifyUsersNoUser IDs to notify on new submissions
notificationNoNotification toggles: { upload, client } — booleans
isAutoAnalyzeNoWhether to auto-analyze submissions
sourceLanguageNoTranscription language code (e.g. en-US)
clientInformationNoRespondent info & questions: { name:boolean, email:boolean, questions:[{ question, isRequired, answerType, options?, includeOther?, fieldId? }], consent?:{ isEnabled, title, description, yesButtonLabel, noButtonLabel, isRequired, fieldId? } }

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoResponse payload from the Speak AI API
Behavior2/5

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

Annotations already indicate readOnlyHint=false (mutation) and destructiveHint=false. The description adds no behavioral context beyond 'Create', such as permissions needed, side effects, or non-destructive nature. No additional value over annotations.

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

Conciseness5/5

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

The description is a single, efficient sentence with no wasted words. It is front-loaded with the action and resource.

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

Completeness2/5

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

Given the tool's complexity (11 parameters, nested objects, output schema exists), the description is too brief. It lacks context on what a recorder entails, return values, or setup considerations. The schema covers details but the description should provide more high-level guidance.

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

Parameters3/5

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

Schema description coverage is 100%, so all parameters are well-documented in the schema. The tool description does not add any parameter semantics beyond what the schema provides, but it implicitly ties the 'audio/video' purpose to options like audio and video booleans. Baseline 3 is appropriate.

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?

The description clearly states the verb 'Create', the resource 'recorder or survey', and the purpose 'collecting audio/video submissions'. This distinguishes it from sibling tools like clone_recorder or update_recorder_settings.

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

Usage Guidelines3/5

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

The description implies usage when a new recorder/survey is needed but provides no explicit guidance on when to use this tool versus alternatives like clone_recorder or when not to use it. No prerequisites or exclusions are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/speakai/speakai-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server