Skip to main content
Glama
Sign In
@speechweave/mcp

@speechweave/mcp

Official
by speechweave
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Start job from URL (async)

start_job_url

Create a transcription job from a public HTTPS URL and receive an immediate job ID for long audio or video files. Poll the job status until completion.

Instructions

Create a transcription job from a public HTTPS URL and return a job id immediately. Use for long media or deferred workflows; poll with get_job_status until completed, failed, or cancelled.

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": {
      "url": "<url>"
    },
    "name": "start_job_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublicly reachable HTTPS URL of the audio or video to transcribe.
modelNoTranscription model tier. core = default balance of speed/accuracy; max = hardest audio.core
languageNoOptional two-letter ISO language code (e.g. en, es).
service_modeNodeferred = background queue (default, better for long audio); synchronous = higher-priority path with a smaller size cap.deferred

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.4/5.0
Behavior4/5

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

No annotations provided, so description must carry burden. It discloses async behavior, job id return, and polling mechanism. Lacks details on rate limits, authentication, or cancellation, but is sufficient for a job creation tool.

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?

Two sentences, no wasted words. Front-loaded with purpose and key usage instruction. Highly efficient.

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

Completeness4/5

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

Given 4 parameters, no output schema, and moderate complexity, description covers main aspects: async flow, polling, and cancellation. Could mention expected job id format, but overall complete.

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 coverage is 100%, so baseline is 3. Description adds minimal extra meaning beyond schema for url (emphasizes 'public HTTPS'). Other parameters not elaborated. Adequate but not exceptional.

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?

Clearly states the verb (create), resource (transcription job from URL), and async nature. Distinguishes from synchronous tools and mentions return of job id.

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

Usage Guidelines5/5

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

Explicitly says 'Use for long media or deferred workflows' and directs to poll with get_job_status. Implicitly contrasts with synchronous alternatives. Provides clear usage context.

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

Deploy Server

Other Tools