ScrapeCreators MCP Server

Transcript

twitter_transcript

Extract the transcript from a Twitter video tweet using AI. Works for videos under 2 minutes; requires confirm=true for paid API calls.

Instructions

Extracts the transcript from a Twitter video tweet using AI-powered transcription. The video must be under 2 minutes long. Returns a success flag and the full transcript text. This endpoint is slower than others due to the AI processing step. Potentially consumes paid API credits; requires confirm=true. Read-like POST requests do not publish to social platforms.

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": "twitter_transcript"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	Tweet URL
`account`	No	Named private ScrapeCreators account; selects credentials, not a remote account ID.
`confirm`	No	Must be true for the specific approved credit-consuming research call.
`cache_max_age`	No	If we have a response in the cache that is this many days old or newer, return the cached response (0 credits, with "cached": true and a "cached_at" timestamp). Otherwise, scrape a live result (1 credit). [See the Caching page for details.](https://docs.scrapecreators.com/caching)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Oct 2, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Adds substantial context beyond annotations: AI processing latency, potential paid credit consumption, confirm=true requirement, and that read-like POST requests do not publish to social platforms. It also states the return shape. Annotations already flag not read-only and open-world, but the description enriches the operational and cost profile.

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?

Front-loaded with purpose, then constraints, return value, performance note, and credit/confirm requirements. Every sentence adds a distinct operational fact with no filler.

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?

Given the rich input schema and absence of an output schema, the description covers purpose, input constraints, side effects, return shape, and confirmation needs. Nothing critical 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?

Schema coverage is 100%, so the schema already documents all four parameters. The description adds the non-schema constraint that the URL must point to a Twitter video tweet under 2 minutes and reinforces the confirm=true requirement, though it does not elaborate on account or cache_max_age.

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?

States a specific verb and resource: extracts a transcript from a Twitter video tweet using AI. It clearly distinguishes itself from sibling transcript tools such as youtube_transcript, facebook_transcript, and instagram_transcript by platform and input type.

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?

The description gives clear constraints: the video must be under 2 minutes, the endpoint is slower, and confirm=true is required. It does not explicitly name alternatives or when-not-to-use cases, but the stated prerequisites effectively scope usage.

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

Deploy Server