Skip to main content
Glama

PostPen

by ai.postpen
OverviewDiscussionsAdmin

Schedule post

schedule_post

Schedules a saved draft, including any media already stored on it by save_draft. scheduled_for is an ISO-8601 timestamp in the future and must include a timezone. destination optionally selects the personal profile or a company page from list_destinations. Media is not accepted here; the images are published with the alt text stored on them, and media_alt_text optionally changes that alt text (one entry per image, in the order of media_urls). The result includes post.preview_url, a link that opens the scheduled post in PostPen; it is meant to be shown to the user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesPost id returned by save_draft.
destinationNoWhere to post: an id from list_destinations. Each destination has a network (linkedin today). "personal" (the default on a personal draft) is the personal LinkedIn profile; a company page is identified by its id from list_destinations (usually the organization URN). On schedule_post and publish_now, leaving it out keeps a company destination already saved on the draft, and "personal" switches to the profile.
scheduled_forYesFuture ISO-8601 time with a timezone, for example 2026-09-28T15:00:00Z.
media_alt_textNoOptional alt text for the images already on the post, one entry per image in the order of media_urls from list_posts. A string (up to 4,086 characters; about 120 recommended) sets that image’s alt text, null or "" removes it, and images past the end of a shorter array keep theirs. Refused when the post has no images or the array is longer than its images.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / media_alt_text
      Added value: +{
+  "description": "Optional alt text for the images already on the post, one entry per image in the order of media_urls from list_posts. A string (up to 4,086 characters; about 120 recommended) sets that image’s alt text, null or \"\" removes it, and images past the end of a shorter array keep theirs. Refused when the post has no images or the array is longer than its images.",
+  "items": {
+    "maxLength": 4086,
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "maxItems": 9,
+  "type": "array"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare non-readonly, non-destructive, open-world, so the safety profile is covered. The description adds real context beyond that: the timestamp must be in the future with a timezone, media is not accepted here, alt text is published with stored images, and the result carries preview_url that is meant to be shown to the user. No auth or rate-limit detail, and no failure modes beyond the alt-text refusal documented in the schema.

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?

Four dense sentences, front-loaded with the core action and constraint before secondary details. Efficient overall, though the future-ISO-8601 phrasing and alt-text ordering restate the schema, which slightly dilutes density.

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?

For a 4-parameter tool with no output schema, the description covers the prerequisite, the routing to list_destinations, the media restriction, and the meaningful return value (preview_url to surface to the user). Missing only edge-case behavior such as scheduling failures or overwriting an existing schedule.

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 baseline is 3. The description reinforces destination semantics (personal profile vs company page) and the ordering of media_alt_text, but most of that content is duplicated in the schema, so it adds little beyond the structured fields.

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+resource ("Schedules a saved draft") and immediately distinguishes itself from the sibling save_draft by naming the prerequisite relationship. Combined with the sibling set (publish_now, unschedule_post), an agent can tell exactly what this tool does without opening a 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?

Clear context: it operates on a draft from save_draft, takes a destination from list_destinations, and explicitly excludes media upload ("Media is not accepted here"). It stops short of stating when to choose this over publish_now or unschedule_post, but the prerequisite and routing references give strong implied guidance.

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

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