Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Copy post to network

copy_post_to_network
Idempotent

Clone an unscheduled draft to LinkedIn, X, or Instagram as a separate draft that shares the same media and is scheduled independently.

Instructions

Copies an unscheduled draft to another network (LinkedIn, X or Instagram) as its own draft, sharing the same media. The copy is scheduled separately.

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": {
      "post_id": "<post_id>",
      "network": "<network>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "copy_post_to_network"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNo
networkYes
post_idYesThe post's id, from list_posts or get_recording.
account_idNo
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=false and idempotentHint=true, and the description adds genuine context: the source must be unscheduled and the copy shares the same media while being scheduled independently. It still does not say whether subsequent edits to the copy diverge from the original, whether media is shared or duplicated, or what identifier comes back (no output schema exists).

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 sentences, front-loaded with the action and source constraint, followed by the scheduling caveat. Every clause carries information; nothing is redundant with the title or restates the name.

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

Completeness2/5

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

For a 5-parameter mutation with no output schema and 20% schema coverage, the description does too little: it omits the idempotency key semantics, the two account-selection parameters, and any indication of what the call returns. What it does say about non-destructiveness and shared media is correct but not sufficient for confident invocation.

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 20%, so the description needs to carry parameter meaning, yet it only maps loosely to `network` by naming the three supported platforms. The required `idempotency_key` and the `account` vs `account_id` disambiguation (different networks vs different teammate accounts) are untouched, leaving two required or conditional parameters unexplained in either place.

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?

States a specific verb and resource (copies an unscheduled draft) plus the destination set (LinkedIn, X, Instagram) and the result (its own draft sharing the same media). An agent can tell this apart from create_post or schedule_post by the 'copies an existing unscheduled draft' framing, though no sibling is named explicitly.

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 precondition 'unscheduled draft' and the note that 'the copy is scheduled separately' imply when this tool is appropriate versus scheduling directly. However, it never states what to do if the source is already scheduled, nor names an alternative such as create_post for building a post from scratch, leaving the agent to infer routing.

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