Skip to main content
Glama

VidGuy

by ai.vidguy
OverviewDiscussionsAdmin

Queue a post on a managed account

publish_to_managed_account
Destructive

Queue a post on a hosted / managed account. Hosted accounts are operated by people, so there is NO publish-now: the post is booked for a day (queueFor, YYYY-MM-DD) and goes live on that day or the next — never promise an exact time. Omit queueFor to take the earliest day the account can accept; get_managed_account_capacity shows that day (posts need a few days' notice, and an account still warming up can only be booked for after warm-up ends) plus which days are already full. Requires a caption plus media: a completed project's video via sourceProjectId, a direct videoUrl, or imageUrls (1 = photo, 2+ = carousel; a TikTok carousel gets a curated sound picked for it unless you pass musicLink). The account must be postable (status 'active'). Costs 20 VidGuy credits per post (402 if the balance is too low; refunded automatically if the post is rejected). Max 2 posts per account per day — a full day returns 409 naming the day. Errors: 400 (day too early / missing sound, with earliestQueueDate), 409 (account not ready / day full). The returned post has status 'scheduled' with scheduledAt on the booked day. NOTE: this creates a real work order and is not retried server-side — never call it twice for the same content. If a call times out, resend it with the SAME idempotencyKey: you get the post the first call created (duplicate: true) instead of a second booking.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
captionYesPost caption (required)
queueForNoDay to queue the post for (YYYY-MM-DD, UTC). Must be on/after the account's earliestQueueDate; omit for the earliest day.
videoUrlNoDirect video URL (alternative to sourceProjectId)
accountIdYesManaged account UUID
imageUrlsNoImage URLs for a photo (1) or slideshow (2+) post
musicLinkNoOptional music/sound link
idempotencyKeyNoYour own unique id for this post (e.g. a UUID). Reuse it to retry safely after a timeout.
sourceProjectIdNoA completed VidGuy project; its rendered video is posted

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes far beyond the annotations: cost (20 credits, 402 on low balance, auto-refund on rejection), the 2-post-per-day cap with 409 behavior, the 'no publish-now / never promise an exact time' constraint, and the no-server-retry plus idempotencyKey recovery path. The 'creates a real work order' warning is consistent with destructiveHint=true and idempotentHint=false, and the idempotencyKey caveat refines rather than contradicts the idempotency annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense and front-loaded, starting with the central scheduling constraint before media requirements and error handling. It runs long with several comma-spliced clauses, but essentially every sentence carries operational information an agent needs.

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 an 8-parameter mutation with no output schema, the description covers the return shape (status 'scheduled' with scheduledAt), the side effects, the error taxonomy, and the retry protocol. Nothing needed to call it correctly 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 baseline is 3, but the description adds real semantics the schema lacks: imageUrls cardinality rules (1 = photo, 2+ = carousel), the auto-picked TikTok sound that musicLink overrides, and the queueFor 'omit for earliest day' behavior. It clarifies intent for sourceProjectId vs videoUrl as alternatives.

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?

The opening sentence names a specific verb and resource ('Queue a post on a hosted / managed account') and immediately clarifies a scope distinction (hosted accounts are human-operated, so no publish-now) that separates it from create_social_post and other posting siblings. An agent can identify the tool 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to omit queueFor, points to get_managed_account_capacity for the earliest acceptable day, enumerates the three mutually exclusive media sources (sourceProjectId, videoUrl, imageUrls), and gives retry guidance with idempotencyKey. It also names the conditions that produce 400/409 so the agent knows when to stop versus adjust.

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

All VidGuy 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