GenFlick

social move posts

native.social_move_posts

DestructiveIdempotent

Atomically move unpinned, unsubmitted events, preserving destination offsets and capacity. social_shift_calendar moves the complete calendar.

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": {
      "work_id": "<work_id>",
      "arguments": "<arguments>",
      "expected_catalog_version": "<expected_catalog_version>",
      "read_skills": "<read_skills>",
      "request_key": "<request_key>"
    },
    "name": "native.social_move_posts"
  }
}

Input Schema

Name	Required	Description
`work_id`	Yes
`arguments`	Yes
`read_skills`	Yes	Exact required native skills and their dependencies, copied from the accepted session bootstrap's skills array. Include only entries in that array. General mcp.* guides and native.{studio}.instructions are guidance, not native skill proofs.
`request_key`	Yes
`publication_proposal_id`	No	For native Social scheduling, the exact server-approved publication proposal. This identifier cannot confer approval by itself.
`expected_catalog_version`	Yes	For a new session, read a studios/{studio}/native/{pack} child toolset and copy invocation.catalog_version from a native tool descriptor. Do not use the top-level library version. For calls in an existing session, use that session proposal's catalog_version.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare destructive, idempotent, openWorld and non-readOnly, so the description's job is to add context — and it does: atomic all-or-nothing semantics, the eligibility filter on unpinned/unsubmitted events, and offset/capacity preservation at the destination. It does not say what happens when a batch contains an ineligible event (reject the whole batch vs. skip), nor does it warn about the read_skills/catalog_version preconditions that any caller must satisfy.

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 with zero filler: the scope and atomicity are front-loaded, then the disambiguation against the sibling. Nothing redundant with the title or schema.

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?

An output schema exists, so return-value explanation is not needed, but this is a destructive, nested-payload, six-parameter tool and the description is thin for that complexity. It omits failure semantics for ineligible events, batch-size expectations (up to 1200 moves), and the session/proof preconditions the schema hints at.

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?

With only 50% schema description coverage, the description should compensate, but it mentions no parameter by name. The phrase "preserving destination offsets" faintly alludes to calendarAnchor, yet work_id, arguments, moves and request_key carry no explanation anywhere, and the required-skills / catalog-version proof pattern is undisclosed in the prose.

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?

Names a specific verb and resource ("move ... events") and narrows scope with two eligibility qualifiers ("unpinned, unsubmitted"). It also explicitly names the sibling social_shift_calendar and what that one does instead, so an agent can distinguish the two 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?

The contrast with social_shift_calendar ("moves the complete calendar") gives a clear routing rule: use this for a targeted subset, use the sibling for the whole calendar. It stops short of an explicit "use this when... do not use when..." statement, and no other alternatives (e.g. single-event edits) are mentioned.

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

All GenFlick tools Inspect

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

Need Help?