postcopilot_download_videoDownload a video from a Threads post URL. Returns direct video download URLs (no watermark). The URL must be a Threads post containing a video (e.g. https://www.threads.com/@user/post/ABC123).
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The Threads post URL containing the video |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description bears full responsibility for behavioral disclosure. It reveals the output behavior (returns direct URLs, no watermark) but omits any discussion of prerequisites (e.g., authentication), error handling for invalid URLs, or rate limits. For a simple read-like operation, this is a minor gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences long with no redundant information. The first sentence states the core purpose and output, and the second clarifies the exact URL format required. Every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with one parameter and no output schema, the description covers the purpose, parameter meaning (with example), and output nature. It does not detail error cases or the exact structure of the return values (e.g., an array of URLs or a single URL), but given the simplicity, the description is nearly complete. A small gap is the lack of note about authentication.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, and the description adds only minimal value beyond the schema. It repeats that the URL must be a Threads post with video and gives an example. While helpful, the schema already describes the parameter with its type and format, so the description does not significantly enhance understanding.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Download a video') and the resource ('from a Threads post URL'). It specifies the output ('direct video download URLs, no watermark') and provides an example URL. This distinctly separates it from sibling tools which handle export, profile, or post generation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly indicates when to use the tool: to download a video from a Threads post URL. It provides context by stating the URL must contain a video. However, it does not explicitly mention when not to use it or suggest alternatives, though the siblings are unrelated enough that the guidance is adequate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: downloading videos, exporting followers/following/profile, generating posts, and reading guides. No overlap or ambiguity.
All tools follow a consistent 'postcopilot_verb_noun' pattern with snake_case, making them predictable and easy to distinguish.
With 6 tools, the server is well-scoped for Threads social media tasks—covering content retrieval, analytics, and creation without being over- or under-sized.
Core workflows (exporting data, generating posts, reading guides) are covered. Minor gaps exist, such as no direct posting or interaction tools, but the surface is coherent for the stated purpose.