Skip to main content
Glama
Upload-Post

Upload-Post

Official

Get a scheduled post

get_scheduled_post
Read-only

Retrieve a scheduled or queued social post by job_id to inspect its settings, signed media URLs, editability, and optional preview or thumbnail for review.

Instructions

One scheduled or queued post by job_id (from list_scheduled). details: the options it was scheduled with (what edit_scheduled can change), signed media URLs and whether it can still be edited. preview: short-lived URLs of its media, cover and thumbnail (null when there is none). thumbnail: a signed URL of a small JPEG of its video or first image, built once if missing; a 202 answer means another request is building it, retry after retry_after seconds.

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": {
      "job_id": "<job_id>"
    },
    "name": "get_scheduled_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNoWhat to return. Default details.
job_idYesThe scheduled post's job_id.

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.26.5

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint annotations: signed vs. short-lived URLs, null returns when no media exists, lazy thumbnail generation, and the async 202 case requiring a retry after `retry_after` seconds. These are exactly the runtime behaviors an agent would otherwise get wrong.

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?

Front-loads the one-line purpose, then enumerates the three views in parallel structure with no filler. The colon-separated fragments are dense but each clause carries distinct information; slightly telegraphic phrasing costs it a point.

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 two-parameter read tool with an output schema, this covers everything action-relevant: id provenance, per-view contents, null cases, and the 202/`retry_after` retry loop. Nothing an agent needs in order 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 meaning to each enum value by specifying the payload each view returns and how `details` relates to what edit_scheduled can change. It stops short of adding format or syntax detail beyond that.

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 resource and scope: 'One scheduled or queued post by `job_id`', and names the sibling that supplies the id (`list_scheduled`). An agent can tell it apart from list_scheduled or edit_scheduled 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?

Explains where `job_id` comes from and routes the caller across the three views by describing what each returns (`details` = scheduling options and editability, `preview` = short-lived media URLs, `thumbnail` = small JPEG). No explicit when-not guidance, but the view selection is effectively usage guidance.

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

Deploy Server

Other Tools