Skip to main content
Glama
Sign In

Any Video to Text

by com.anyvideototext
OverviewDiscussionsAdmin

List my saved transcripts

list_my_transcripts
Read-onlyIdempotent

List the video transcripts this account has kept in My transcripts, newest first, 100 at a time. Search with query, which looks through titles, creators and what was said. Open one with get_my_transcript.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_my_transcripts"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoWords to look for. Leave out to list everything.
offsetNoHow many to skip, to get the next page when more is true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: newest-first ordering, a 100-item page size, and what the search covers. Return shape beyond ordering is still implicit.

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, all front-loaded with the listing semantics first and the search/open guidance after. No filler.

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?

For a simple two-param read tool with full annotations and no output schema, the description covers purpose, ordering, paging and search scope. Only the exact response shape and the meaning of a 'more' indicator are left implicit.

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 100%, so both parameters are documented; the description nevertheless adds real meaning by specifying that query searches titles, creators and spoken content, not just one field. It doesn't detail offset/pagination mechanics beyond what the schema says.

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?

Names a specific verb (list), a specific resource (video transcripts kept in My transcripts), plus ordering and page size. It is clearly distinguishable from get_my_transcript and the other siblings.

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?

Explicitly routes the agent: use 'query' to search, and use get_my_transcript to open a single item. It doesn't state exclusions (e.g., when to prefer get_transcript vs this list), so it stops short of full when/when-not guidance.

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

All Any Video to Text toolsInspect
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