Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Send clip to scheduling

send_clip_to_scheduling
Idempotent

Creates or restores a clip's draft post in Scheduling, without scheduling or publishing it.

Instructions

Creates the clip's draft post in Scheduling, or brings back the draft if it was deleted. Does not schedule or publish it.

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": {
      "clip_id": "<clip_id>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "send_clip_to_scheduling"
  }
}

Input Schema

NameRequiredDescriptionDefault
clip_idYesThe clip's id, from list_recordings or get_recording.
account_idNo
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, open-world. The description adds genuinely new behavior: it creates a draft rather than a live post, and it resurrects a previously deleted draft instead of failing or duplicating. It does not describe what is returned or what happens to clip state afterward.

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?

Two short sentences, front-loaded with the core action and followed by the scope exclusion. Every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should say what the caller gets back (a draft id, a post object) and what idempotency_key should hold. It covers the mutation semantics well but leaves those gaps for a mutation tool with a required undocumented parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%; clip_id and account_id are documented in the schema, but idempotency_key — a required parameter — has no explanation anywhere. The description adds no parameter meaning of its own to compensate for that gap.

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?

Uses a specific verb and resource: 'Creates the clip's draft post in Scheduling,' and adds a restore case. The negative clause 'Does not schedule or publish it' rules out a plausible misreading, though no sibling tool is named for contrast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The 'does not schedule or publish' clause implies the boundary against scheduling/publishing actions, and the restore behavior signals it is safe to retry. There is still no explicit guidance on when to prefer this over create_post or another drafting path.

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