Skip to main content
Glama
Sign In

PostToData

by com.posttodata
OverviewDiscussionsAdmin

Transcript

get_transcript
Read-only

The full spoken text of one video, with a timestamp for every line. Returns compact, cited results (each item has a url). Works on: youtube. Requires a prepaid API key.

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": {
      "platform": "<platform>",
      "id": "<id>"
    },
    "name": "get_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPost ID, or the public URL of the post.
langNoTranscript language code such as en, es or ja. Default: English when the video has it, otherwise the video's own captions.
platformYesWhich platform to read. Live now: Bluesky, Hacker News, YouTube, Reddit, X (Twitter), TikTok, Instagram, Threads, Xiaohongshu (RedNote), Douyin.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond readOnlyHint/openWorldHint, the description adds real behavioral context: per-line timestamps, compact cited items each carrying a url, YouTube-only scope, and a prepaid API key requirement. That auth prerequisite is exactly the kind of detail annotations cannot convey.

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, zero filler, with the core purpose front-loaded and the platform and auth caveats trailing in order of importance.

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?

With no output schema, the description does carry some return-value burden and discharges it partially by describing timestamps and cited url-bearing items. For a three-parameter read tool with full schema coverage, this is close to complete, with only result shape detail (pagination, item fields beyond url) left unspecified.

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 the schema already documents id, lang, and platform. The description only indirectly reinforces that id targets a single video and that platform is limited to youtube; it adds nothing about language selection behavior, which the schema handles.

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?

States a specific verb and resource: the full spoken text of one video, with a timestamp for every line. That distinguishes it from get_post and get_comments well enough, though no sibling is named explicitly.

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?

'Works on: youtube' sets a hard platform constraint and implies the caller should use this only for YouTube video transcripts. However, there is no explicit when-to-use versus get_post or get_comments, and no 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 PostToData 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