GimmeText

Create upload link

create_upload_link

Use when the user wants to transcribe a recording they have on their device. The link page accepts any video or audio file. Give them the link, ask them to drop the file there, then poll get_job.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`url`	Yes	Single-use upload page URL. Open it and drop the file.
`single_use`	Yes	Always true; the link works once.
`upgrade_url`	No	Present when the user is nearly or fully out of minutes: where to add hours or upgrade.
`remaining_seconds`	No	Seconds of transcription the user has left (monthly minutes plus any hour pack).
`expires_in_minutes`	Yes	Minutes until the link expires.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 22, 2026

addedOutput schema / properties / remaining_seconds

Added value: +{
+  "description": "Seconds of transcription the user has left (monthly minutes plus any hour pack).",
+  "type": "number"
+}

addedOutput schema / properties / upgrade_url

Added value: +{
+  "description": "Present when the user is nearly or fully out of minutes: where to add hours or upgrade.",
+  "type": "string"
+}

Changed1 schema field changedOct 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "expires_in_minutes": {
+      "description": "Minutes until the link expires.",
+      "type": "number"
+    },
+    "single_use": {
+      "description": "Always true; the link works once.",
+      "type": "boolean"
+    },
+    "url": {
+      "description": "Single-use upload page URL. Open it and drop the file.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "url",
+    "expires_in_minutes",
+    "single_use"
+  ],
+  "type": "object"
+}

First observedOct 11, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare this is not read-only, not idempotent, and not destructive, so the safety profile is covered. The description adds useful behavioral context beyond that: the link accepts any video or audio file, the user must perform the upload, and the agent must subsequently poll get_job. It does not cover link expiry or reuse limits, which keeps it from a 5.

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?

Three short sentences, front-loaded with the usage condition and followed by the exact workflow. Every sentence carries actionable information with no repetition of schema or annotation data.

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?

For a zero-parameter tool with an output schema, the description supplies what the structured fields cannot: the triggering situation, the fact that the user performs the upload, and the required next call to get_job. Nothing essential for correct invocation 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?

There are zero parameters, so there is no parameter semantics for the description to clarify. The baseline for a no-parameter tool applies.

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

Purpose4/5

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

The description identifies the action (give the user an upload link) and the resource (a link page accepting any video or audio file), and the follow-up poll of get_job separates it from the sibling read tools. It is clear, though the core verb 'create a link' is implied through 'Give them the link' rather than stated as a definition.

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?

It states an explicit trigger ('Use when the user wants to transcribe a recording they have on their device') and then gives the full operating sequence: hand over the link, ask the user to drop the file, then poll get_job. The sibling alternative for the next step is named directly, leaving little to infer.

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

All GimmeText 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?