Skip to main content
Glama

Get Submission Tool

get-submission-tool
Read-only

Fetch a single video submission the authenticated user is allowed to view, on any platform — TikTok, Instagram or YouTube. Use it to poll a submission until status is final. Statuses: scheduled (waiting for scheduled_at), pending (queued), ingesting (sending the video to the phone), driving (the phone is posting), then one of the final states published, drafted, failed (see failure) or cancelled.

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": {
      "submission_id": "<submission_id>"
    },
    "name": "get-submission-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
submission_idYesID of the submission to fetch, on any platform.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/closed-world, and the description goes well beyond them by disclosing the full status lifecycle (scheduled → pending → ingesting → driving → terminal), naming the terminal states, and pointing at `failure` for error detail. That is exactly the behavioral context an agent needs to interpret polling results and decide when to stop.

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 sentences: what it fetches, when to use it, and the state machine. The usage cue and the polling guidance are front-loaded, and the parenthetical glosses on each status carry real information rather than filler.

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?

There is no output schema, so the description carries the burden of explaining return values; it handles `status` and `failure` thoroughly but says nothing about the rest of the payload (media, timestamps, IDs). Access scoping ('allowed to view') implicitly covers permission failures, making the definition otherwise sufficient for a simple read tool.

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?

With only one parameter and 100% schema description coverage, the schema already fully documents `submission_id`. The description merely repeats that the ID works 'on any platform', adding no format, range, or lookup guidance beyond the structured field, 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?

The description opens with a specific verb and resource ('Fetch a single video submission') and constrains scope to what the authenticated user may view, which also implicitly separates it from the list-submissions sibling. An agent can tell immediately this is a single-record read, not a listing or a mutation.

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?

It gives an explicit use case — 'poll a submission until `status` is final' — which tells the agent exactly when to reach for this tool rather than list-submissions or a run tool. It stops short of naming alternatives or stating when not to use it (e.g. bulk retrieval), so it falls just below a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources