Skip to main content
Glama

0bull Phone Farm

by net.0bull
OverviewDiscussionsAdmin

Create Submission Tool

create-submission-tool

Queue a video to be published to a TikTok, Instagram or YouTube account. Set platform (defaults to tiktok) and account_id. Provide the video via exactly one of video_url (a public https link the server downloads) or upload_id (from create-upload-url-tool). The account must be assigned to a phone. Set scheduled_at to publish later instead of now; a scheduled submission can be cancelled with cancel-submission-tool until it starts. Returns the submission; poll get-submission-tool for the outcome.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
draftNoSave as a draft on the phone instead of publishing. Supported on all three platforms.
captionNoText for the post: up to 2200 characters on TikTok and Instagram. On YouTube this is the Short's TITLE — required, and capped at 100 characters.
platformNoPlatform to post to: "tiktok" (default), "instagram" or "youtube".
upload_idNoUpload id from create-upload-url-tool. Mutually exclusive with video_url.
video_urlNoPublic https URL of the video. Mutually exclusive with upload_id.
account_idNoID of the account to post as, from list-accounts-tool. The account must be on `platform`. Required unless the deprecated tik_tok_account_id is given.
webhook_urlNoPublic https URL to POST to once the submission reaches a final status (published, drafted, failed or cancelled), for a system that cannot poll. The body is the submission, signed with an X-0bull-Signature header the same way as REST API webhooks. Optional.
scheduled_atNoWhen to publish, as an ISO 8601 timestamp in the future, e.g. "2026-10-01T18:00:00+02:00". A timestamp without an offset is read as UTC. Omit to publish now. The submission is created with status "scheduled" until then.
tik_tok_account_idNoDeprecated alias for account_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / account_id / description
      Previous value: -"ID of the account to post as. Required unless the deprecated tik_tok_account_id is given."New value: +"ID of the account to post as, from list-accounts-tool. The account must be on `platform`. Required unless the deprecated tik_tok_account_id is given."
    • addedInput schema / properties / platform / enum
      Added value: +[
+  "tiktok",
+  "instagram",
+  "youtube"
+]
    • changedInput schema / properties / upload_id / description
      Previous value: -"Upload id from create_upload_url. Mutually exclusive with video_url."New value: +"Upload id from create-upload-url-tool. Mutually exclusive with video_url."
    • addedInput schema / properties / webhook_url
      Added value: +{
+  "description": "Public https URL to POST to once the submission reaches a final status (published, drafted, failed or cancelled), for a system that cannot poll. The body is the submission, signed with an X-0bull-Signature header the same way as REST API webhooks. Optional.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / scheduled_at
      Added value: +{
+  "description": "When to publish, as an ISO 8601 timestamp in the future, e.g. \"2026-10-01T18:00:00+02:00\". A timestamp without an offset is read as UTC. Omit to publish now. The submission is created with status \"scheduled\" until then.",
+  "type": "string"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly=false, openWorld=true, destructive=false, so the safety profile is covered. The description adds real behavioral context beyond that: the account-must-be-assigned-to-a-phone prerequisite, the exactly-one-of video source constraint, and the scheduled status lifecycle. It is silent on auth requirements, rate limits, and idempotency, keeping it short of 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?

Five tightly packed sentences with the core action front-loaded, then defaults/constraints, then scheduling, then the return/poll path. No filler; every sentence carries operational information.

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 9-parameter mutation tool with no output schema, the description covers the return value ('Returns the submission') and the follow-up polling route, plus the key prerequisites. Nothing an agent needs to invoke it correctly is missing.

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 description coverage is 100%, so the schema already documents defaults, mutual exclusivity, and field semantics. The description largely restates what the schema provides (tiktok default, exactly-one-of video_url/upload_id) without adding new format or syntax detail, so the baseline 3 applies.

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 ('Queue a video to be published') plus the exact target platforms, immediately distinguishing it from sibling list/get/cancel submission tools. An agent knows this is the creation entry point without opening the schema.

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?

Gives conditional routing: use scheduled_at to publish later, cancel a pending schedule with cancel-submission-tool, and poll get-submission-tool for the outcome; upload_id references create-upload-url-tool as its source. It never states an explicit 'do not use this when...' exclusion, but the alternative-condition guidance is clear.

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

All 0bull Phone Farm 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