Skip to main content
Glama

ADS Beast

prepare_social_post_schedule

Prepare publishing or scheduling a post on a client's connected social channel. Changes nothing: stores a preview_id (15 min, single use) to show, then execute_prepared_change.

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": {
      "client_id": "<client_id>",
      "platform": "<platform>",
      "text": "<text>",
      "reason": "<reason>"
    },
    "name": "prepare_social_post_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesPost text.
reasonYesWhy, with numbers (shown to the approver).
platformYesmeta_page, linkedin, telegram or instagram.
client_idYes
image_urlNoPublic https URL of an image.
scheduled_atNoISO date-time; without it the post goes out on approval.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With annotations already declaring readOnlyHint=false, openWorldHint=true, and destructiveHint=false, the description adds genuinely useful behavior: no side effects on the channel, plus the returned preview_id is short-lived (15 minutes) and single-use. Those TTL and single-use constraints are exactly the kind of detail annotations cannot express. Minor tension exists between 'changes nothing' and readOnlyHint=false, but it is resolved by the fact that a preview token is stored, so it is not a contradiction.

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?

Two tight sentences, front-loaded with the action and immediately followed by the crucial 'changes nothing' constraint and the follow-up tool. The second sentence is telegraphic ('to show, then execute_prepared_change'), which trades a little readability for brevity, but nothing is wasted.

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, and the description still tells the agent what the call produces (a preview_id) and its lifetime, which is the key return-value information. Six parameters with four required are well covered by the schema. The one gap is that the approval step implied by the required 'reason' parameter is not connected explicitly to the workflow, but the essential call mechanics are complete.

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 83%, with text, reason, platform, image_url, and scheduled_at all documented in the schema, so the baseline is 3. The description adds only the implied notion that scheduling is optional ('publishing or scheduling'), which the scheduled_at field already covers. No additional meaning about client_id or the approval audience is contributed beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource: preparing (not performing) a publish or schedule action on a client's connected social channel. It also distinguishes itself from execute_prepared_change by stating it 'changes nothing,' so an agent can see it is the staging half of a two-step flow. Slightly less than perfect because 'Prepare publishing or scheduling' is a bit compressed, but the intent is unambiguous.

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 clear context: this is the staging step that returns a preview_id for the user to see, followed by execute_prepared_change to actually apply it. That implicitly tells the agent not to expect the post to go live from this call. There is no explicit statement of when not to use it (e.g., when a preview already exists or has expired beyond 15 minutes), but the workflow guidance is strong.

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.